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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds only the returned field list and the raw endpoint (GET /tasks); it says nothing about pagination behavior or result limits beyond what the schema documents.

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?

A single compact sentence with the returned fields front-loaded in a parenthetical and the endpoint appended. No filler, nothing repeated from the schema.

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?

For a read-only list tool with full schema coverage and no output schema, listing the returned fields compensates well for the missing return value documentation. The only gap is pagination/result-set guidance, which the page and per_page descriptions largely cover indirectly.

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 100%, so all five parameters (page, sort, complete, per_page, customer_id) are already fully documented in the schema. The description's mention of 'whether complete' lightly echoes the complete filter but adds no syntax or format detail. Baseline 3 applies when the schema does the heavy lifting.

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?

States a specific verb (List) and resource (collection tasks) and enumerates the returned fields, so the agent knows exactly what comes back. It does not distinguish itself from sibling list tools (e.g. invoiced_list_events or invoiced_list_notes) beyond the resource noun, but the resource is unambiguous.

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?

Usage is only implied: the name and endpoint make it obvious this is the read path for tasks, and 'whether complete' hints at filtering. There is no statement of when to prefer this over invoiced_create_task, invoiced_list_events, or per-customer fetching, and no exclusions.

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