list-tasks

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

Without annotations, the description carries the full burden of behavioral disclosure. It implies a read-only operation via 'List', but it does not mention the pagination parameters (page, limit) that control the result set, nor does it clarify that 'all tasks' may be limited. This could mislead an agent about the completeness of the returned list.

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, front-loaded sentence with no redundant words. It delivers the core message efficiently, making it highly concise and easy to parse.

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 tool has four parameters including pagination controls, and no output schema. The description omits any mention of pagination or response format, leaving the agent without key usage information. Additionally, it does not clarify how this listing tool relates to create-task or other task-oriented tools.

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 description mentions the status filter, aligning with the status parameter, but it adds no meaning to page, limit, or case_id beyond the schema. With only 50% schema description coverage, the pagination parameters (page, limit) remain undocumented in both schema and description, leaving a significant gap.

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') and resource ('tasks') with a clear scope ('for a specific case') and an optional filter ('by status'). This clearly distinguishes it from sibling list tools like list-notes and list-documents.

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 when tasks for a known case are needed, but it does not explicitly state when to use this tool over alternatives such as create-task or list-cases. No exclusions or alternative references are provided.

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