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

Annotations already declare readOnlyHint=true, openWorldHint=false, destructiveHint=false, so the safety profile is fully covered by structured data. The description's only added behavior detail is 'with its findings', which marginally implies the payload includes finding objects but says nothing about size, pagination, or failure modes.

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 no filler and the verb front-loaded. It is efficient but borders on under-specification rather than being genuinely tight prose.

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 three required parameters, zero schema descriptions, and no output schema, the description needs to carry more weight than one sentence. It never explains what a diagnosis ID is, how to obtain one, or what 'findings' contain, so an agent lacks the context needed to call it confidently.

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% and all three parameters (projectId, siteId, diagnosisId) are undocumented in both schema and description. The names are largely self-evident, but the description gives no format, source, or relationship guidance, leaving the description to compensate for the coverage gap and failing to do so.

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 ('Read') and a specific resource ('one traffic drop diagnosis') and adds that findings are included, which separates it from the list/summary siblings. It never names `list_seo_diagnoses` or any other sibling explicitly, so the differentiation is inferable rather than stated.

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 guidance on when to call this versus `list_seo_diagnoses`, `get_seo_health`, or `list_seo_changes`, and no hint that the required IDs typically come from a preceding list call. The agent must infer the whole workflow.

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