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

Annotations already declare readOnly, idempotent, and non-open-world. The description adds meaningful behavior beyond that: derivedFrom tasks are blocked, appear last, and cannot be ordered, and the list includes fix and verification instructions.

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 scope and the sibling alternative are front-loaded and there is little waste. The middle sentence about fix and verification instructions is slightly loose, but the description remains compact and purposeful.

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?

With no output schema, the description still explains the key non-obvious return semantics: derivedFrom blocking, ordering constraints, and included instruction content. Minor omissions around pagination and exact return shape are acceptable for a read-only list tool.

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 limit, locale, status, and site_id are already documented in the schema. The description adds no parameter-level detail, which is acceptable at baseline 3 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 and resource ('Full task list for a website') and distinguishes itself from the sibling get_site_brief, which it names explicitly. An agent can tell this is the list-all-tasks tool rather than a brief or a single-fix retrieval.

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?

Gives clear routing guidance: 'for the top 3 decisions call get_site_brief first', and notes that derivedFrom tasks cannot be ordered, which points toward order_fix limits. It lacks explicit when-not-to-use exclusions, but the alternative and its condition are stated.

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