List due tasks

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

Annotations already declare readOnlyHint=true and idempotentHint=true, indicating safety. The description adds that the tool lists 'open' tasks, suggesting a status filter. No contradictions.

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 one concise sentence that delivers the core purpose without wasted words. However, it could be slightly expanded to cover parameter details.

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 covers the main function but is incomplete on parameter semantics. An output schema exists, so return values are handled, but parameter details are lacking.

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?

Schema description coverage is 0%, so the description should compensate. It mentions 'N days' and 'overdue' but does not explicitly map to parameters like 'days', 'user', 'limit', or 'include_overdue'. Parameter names are somewhat self-explanatory, but the description lacks detail.

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 states the tool lists 'open care tasks due within N days, optionally including overdue tasks.' The verb 'List' and resource 'open care tasks' are specific, and the filtering criteria distinguish it from sibling tools like list_care_tasks.

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?

While the description does not explicitly state when to use or avoid this tool versus alternatives, the context of due tasks within a timeframe is clear enough for an agent to infer appropriate usage. No exclusions are stated.

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