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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered structurally. The description adds essentially nothing on top: no mention of whether results expire, persistence of the analysis, or why idempotentHint is false for what reads like a fetch. The implicit prerequisite is the only extra signal.

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 short sentence with the resource front-loaded and zero waste. It is efficient, though its extreme brevity borders on under-specification rather than model conciseness.

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?

There is no output schema, so the description would ideally hint at the shape or size of results (the detail param hint partially covers size). For a low-complexity 2-param read tool with full schema coverage and safety annotations, this is minimally adequate but leaves the agent guessing about return content.

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%, with the detail parameter well documented (concise vs detailed, top-25 trimming) and analysis_id described. The description adds no parameter meaning of its own, so the baseline 3 applies when the schema carries the full burden.

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 (get) and resource (results of a previously run SEO analysis), which is clearer than a bare tautology. It does not distinguish itself from nearby siblings like list_analyses, run_analysis, or get_report, so the agent must infer the distinction rather than being told.

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?

"Previously run" implies a prerequisite (an analysis must already exist), giving some implied usage context. However, there is no explicit statement of when to use this versus list_analyses (discovery) or run_analysis (execution), and no mention of what to do if the analysis ID is unknown.

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