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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds modest context: the data is 'retained normalized' content and dataset references are 'owner-scoped' (an authorization hint), plus a scope exclusion. It does not cover not-found behavior or how ownership is enforced.

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?

Two short sentences with the operative content front-loaded and no filler. It is efficient, though the second sentence is a scope disclaimer rather than an operational detail, so it is lean rather than optimally informative.

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 an output schema present, return values need not be explained, and the safety profile is handled by annotations. However, for a lookup tool the description omits how the analysis_id is obtained and how this differs from list_analyses, leaving meaningful gaps for correct invocation.

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 the single required parameter, so the description must compensate and does not: it says nothing about analysis_id, its UUID form, or that it comes from list_analyses. The schema supplies only type/format, leaving the agent without provenance or meaning for the argument.

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 verb 'Read' is present, but the description never names the resource it returns (an analysis) and instead enumerates payload contents ('normalized inputs, operations, results and owner-scoped dataset references'). A reader can infer it fetches a stored analysis record, but it is not contrasted with the sibling list_analyses, so single-vs-list selection is left to inference.

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 only guidance is a negative scoping statement ('This is not an external agent transcript'), which excludes a category rather than stating when to call this tool. There is no mention of when to prefer get_analysis over list_analyses or where the required analysis_id originates.

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