list_todos

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does not mention pagination, default limits, response format, or any side effects. Listing could imply read-only, but that is not explicitly stated, and there is no detail about how filtering/sorting behaves.

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 concise sentence that is front-loaded with the verb 'List' and the object 'TODOs'. It contains no redundant words and earns its place.

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?

Given a modest 6-parameter list tool with no output schema, the description is sufficient but minimal. It lacks guidance on defaults like sortBy or pagination, and does not address how this tool differs from search_todos, leaving some gaps for an agent deciding which tool to invoke.

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 has 100% description coverage, with all six parameters individually described including enums and defaults. The description adds no extra meaning beyond the schema, which is acceptable given the high schema coverage, but it does not compensate for any missing context.

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 uses a specific verb 'List' with resource 'TODOs' and mentions optional filtering and sorting, making the core purpose clear. However, it does not differentiate from the sibling 'search_todos', so it lacks sibling distinction.

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 phrase 'optional filtering and sorting' implies when to use (listing with simple filters), but there is no explicit guidance on when not to use it or when to prefer 'search_todos' or other siblings. Context is implied, not stated.

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