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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds one real behavioral fact — that the full (untruncated) text body is returned — but says nothing about failure modes when an ID is unknown or about permissions.

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 with no filler and the scope constraint ('one') placed before the resource. Efficient, though its brevity leaves the under-specification unaddressed.

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 tool requiring three undocumented identifiers and returning full text with no output schema, the description is too thin — it does not indicate the ID hierarchy, expected return shape, or the error behavior for a missing run.

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% for three required parameters (projectId, siteId, runId), and the description supplies no parameter meaning at all. It does not explain that the IDs must form a consistent hierarchy or where they are obtained, so it 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?

States a specific verb ('Read') and resource ('one recorded AI answer') and scopes it to a single record, which contrasts with the several list_* siblings. It does not, however, clarify how an 'AI answer' relates to the sibling concepts list_ai_visibility_prompt_runs or get_ai_visibility_citations, so the agent must infer the relationship.

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?

No when-to-use guidance, no prerequisites, and no named alternative. The agent is left to infer that this is called after listing prompt runs to retrieve one answer's text, which is implied at best.

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