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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorld, so the safety profile is covered. The description adds genuinely new behavioral context — "No authentication required" and the guarantee that no site re-scan is triggered. It does not cover failure behavior for a stale or unknown report_id, which keeps it at 4.

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 pairs the action with the key constraint (use the existing report_id, no re-scan), then appends the auth note. No redundant or filler wording.

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 one-parameter retrieval tool with rich annotations, the description covers what the tool does, where the ID comes from, and the auth/side-effect profile. The one gap is that no output schema exists and "full AX Audit report" is left vague, so the agent gets no sense of the returned report's structure.

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 single parameter is fully documented in the schema as coming from a prior run_full_audit call. The description restates that same origin rather than adding format, validity, or expiry details, so the schema is doing 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?

The description uses a specific verb and resource ("Fetch a full AX Audit report") and pins it to the "report_id returned from run_full_audit," which directly separates it from the siblings run_full_audit and scan_site. An agent can choose this tool over re-scanning without opening the schema.

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?

It gives clear usage context: call this after run_full_audit has produced a report_id, and the point of the tool is to avoid re-scanning the site. It never states an explicit exclusion (e.g., "do not use if the report has expired"), so it falls just short of the top band.

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