basecamp_list_todos

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

With no annotations, the description carries the full burden, but it only states a list operation, which inherently suggests read-only. It does not disclose whether filters affect results, whether pagination occurs, or any default behavior regarding archived/completed to-dos, leaving some ambiguity.

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?

The description is a single, short, front-loaded sentence. Every word is meaningful, and it immediately conveys the core function without redundancy.

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?

The description does not mention the optional filters (status, completed) or what the default return set comprises (e.g., active only). Since no output schema exists, it also does not describe the structure of returned to-dos, making the description less complete than it could be for a 4-parameter tool.

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 input schema provides descriptions for all four parameters, giving 100% coverage. The tool description adds no additional parameter context beyond what the schema already states, so it neither helps nor hurts.

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?

The description clearly identifies the action ('List') and the specific resource ('all to-dos in a to-do list'), distinguishing it from single-todo retrieval (get_todo) and creation (create_todo). It unambiguously answers what the tool does.

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?

The description implies usage for retrieving a collection of to-dos within a given list, but it does not provide explicit guidance on when to choose this over alternatives like get_todo, nor any exclusionary conditions. This leaves the agent to infer from the tool name and context.

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