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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds genuine behavioral context beyond those annotations: the result is a flat list (not nested), sorted by status then position, and agents must use parentId to reconstruct the tree. Minor gaps remain (no mention of result limits or whether all statuses are included), but the disclosed behavior is substantive.

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, zero filler. The core purpose and output behavior are front-loaded in the first sentence, and the routing guidance lands in the second. Every clause earns its place.

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 low-complexity read-only tool with full schema coverage, safety annotations, and no output schema, the description carries the return-semantics burden and does so thoroughly: it explains the flat structure, ordering, and how to rebuild the subtask hierarchy, and routes count-only needs elsewhere. Nothing essential for correct invocation is missing.

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% and the schema already documents projectId as 'The project whose tasks to list.' The description adds only the 'standalone' qualifier and implicit scope via its own text, which is marginal. With full schema coverage, the baseline of 3 applies; the description does not substantially deepen parameter meaning.

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 states a specific verb and resource ('List all tasks in a standalone project') and goes further by specifying output shape (flat list), ordering (status then position), and hierarchy semantics (parentId for subtask trees). It also distinguishes itself from get_standalone_project_summary, so an agent can reliably pick it apart from the closest sibling without opening schemas.

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 second sentence gives an explicit when-not-to-use rule with a named alternative: 'Use get_standalone_project_summary instead if you only need counts, not the full task list.' This is exactly the kind of routing guidance that helps an agent make the correct selection.

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