List Project Tasks

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

Description adds pagination and 'never returns long content' beyond annotations which already declare readOnlyHint, destructiveHint, idempotentHint, and openWorldHint. 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?

Two concise sentences. First explains what the tool does; second provides usage workflow. No filler words.

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 no output schema, description adequately describes return as paginated task summaries. Also provides workflow context with sibling tool, making it complete for decision-making.

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 coverage is 100%, baseline 3. Description adds value by tying parameters to functionality: mentions filtering by type/status and pagination, and clarifies the project parameter is the path variable.

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 it calls GET /projects/{project}/tasks and returns paginated task summaries only, distinguishing it from sibling aiproject_get_task which retrieves a single task with full content.

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?

Explicitly says to use this tool to scan tasks and optionally filter before calling aiproject_get_task for a selected task, providing clear guidance on when to use and the alternative.

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