list_tasks

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. Description adds behavioral traits: 'bounded pagination' implies limit and offset are enforced, 'allowlisted sorting' indicates only specific sort fields. No contradictions with annotations. Additional context like rate limits or empty result behavior is missing.

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?

Single sentence, front-loaded with verb and resource. Every phrase adds value ('bounded pagination', 'allowlisted sorting'). However, it could be slightly expanded to include the status filter without losing conciseness.

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 the output schema exists (documenting return structure) and annotations cover safety, the description is mostly adequate. However, it fails to mention the status filter, a key parameter. Pagination and sorting are addressed. Overall, a minor gap reduces completeness.

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 description must compensate. It only mentions pagination and sorting in general terms, but does not specify the parameters (limit, offset, sort_by, sort_order) or the status filter. No parameter details or syntax are provided, leaving agents to infer from schema alone.

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?

Description clearly states verb 'List' and resource 'tasks', with constraints 'bounded pagination' and 'allowlisted sorting'. It distinguishes from sibling tools like get_task (single) and create_task/modify tasks. However, it omits mentioning the status filter parameter, which is a notable missing aspect.

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?

No explicit guidance on when to use this tool versus alternatives. The description does not mention when not to use it (e.g., for single record retrieval, use get_task). Siblings are listed but not referenced. Agent must infer usage context from the name alone.

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