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

The readOnlyHint annotation already establishes the safe-read profile, lowering the bar, but the description adds almost nothing beyond that. It does not disclose pagination, size limits, or auth needs, and 'full structured agent contract' is vague about what is actually returned.

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 sentence with no waste, but it is under-specified rather than efficiently complete. The one clarifying detail (slug or URL path) is useful yet insufficient for the tool's complexity.

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?

An output schema exists so return values need not be explained, but with 4 parameters at 0% coverage and a page/task naming mismatch, the description is not complete enough for an agent to invoke the tool confidently. It should at least cover the core parameters and the task-vs-page distinction.

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 0% across 4 parameters. The phrase 'by slug or URL path' only loosely maps to the required 'path' parameter, and locale, section, and maxChars are entirely undocumented in both schema and description. The description fails to compensate for the coverage gap.

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 verb (Read) and a resource (the full structured agent contract), but the noun 'page' conflicts with the tool name read_task and title 'Read a documented task', and it doesn't distinguish itself from the sibling read_page. An agent cannot easily tell when to use read_task versus read_page based on this text.

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?

There is no indication of when to use this tool versus alternatives like read_page or list_tasks, and no prerequisites or context are given. Usage is left entirely to inference from the sibling names.

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