list_topics

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full behavior burden, and it does add real domain semantics by clarifying that 'topics' encompasses messages and forwards (not just messages). However it says nothing about result volume, pagination, ordering, or permissions, which matters for a list endpoint over an entire project.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

One short, front-loaded sentence with the scope constraint at the end and no wasted words. It is arguably terse, but nothing extraneous is present.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter list tool with no output schema, the definition covers what the agent needs to invoke it. Minor gaps remain around pagination/result handling and whether archived topics are included.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter is fully documented in the schema (100% coverage), so the baseline is 3. The description only loosely ties project_id to 'a Basecamp 2 project' and adds no format or ID-sourcing guidance beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb (List) plus resource (topics) scoped to a Basecamp 2 project, with a parenthetical that defines what a 'topic' actually is (messages, forwards, etc.). This clearly separates it from siblings like get_message or list_todos, though it doesn't explicitly name a competing tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by the scoping phrase 'in a Basecamp 2 project' — the agent can infer it needs a project_id and that this is the project-wide topic feed. There is no explicit when-to-use, when-not-to-use, or alternative tool named.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.