list_tasks

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

Annotations already declare read-only and idempotent behavior. Description adds that results are compact summaries with has_more indicator and that limit is capped at 100. However, pagination behavior (offset usage) and error scenarios are not described.

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 sentences, front-loaded with action and filtering nature. No wasted words; structure is efficient.

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?

Despite having output schema, the description fails to cover the semantics of most input parameters (5 of 7 undocumented). Pagination via offset and has_more is implied but not explained. Lacks details on ordering or other constraints.

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?

With 0% schema coverage, description must clarify parameters. Only assigned_to (comma-separated UUIDs) and limit (capped at 100) are explained. The other five parameters (title, offset, column_id, sticker_id, sticker_state_id) are left undocumented, requiring inference.

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 lists tasks with server-side filters and distinguishes itself from get_task by noting it returns compact summaries with has_more. Purpose is unambiguous and differentiates from sibling.

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 tells when to use get_task for full objects and notes limit cap of 100. Lacks guidance on when to use alternative list tools or pagination usage, but provides sufficient context for basic use.

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