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

Annotations declare readOnlyHint=true, and the description adds that the data comes from the latest deep scan, implying a dependency on a scan having been performed. This is extra context beyond the read-only annotation, but it does not disclose what happens if no scan exists or if the scan is stale.

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, front-loaded sentence that conveys the purpose, content, and ordering without extraneous detail. Every clause earns its place, and the structure is efficient for an agent to parse quickly.

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 simple read-only tool with no parameters and no output schema, the description provides sufficient context: what it returns (prioritized fix list) and its ordering. It doesn't mention potential edge cases like absence of a scan, but that is acceptable given the tool's simplicity and the presence of sibling request_rescan.

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?

The tool has zero parameters and an empty schema, so there is nothing to describe. Baseline for 0 params is 4; the description adds no parameter-related information, which is appropriate given the schema coverage is 100% and no params exist.

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 clearly states the tool returns a prioritized fix list from the latest deep scan, specifying the content (specific changes to improve AI answers) and ordering (highest impact first). This distinguishes it from sibling tools like get_answers or get_benchmark, which focus on other data.

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 description implies usage after a deep scan ('latest deep scan') but does not explicitly state when to use this tool over alternatives or when not to use it. No exclusions or alternative tool names are provided, leaving the agent to infer context from sibling names.

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