get_diagnostic_result

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

With no annotations, the description must disclose behavior on its own. It adds some context by saying the result is 'stored' and that all attempts are returned, which implies a read operation, but it does not state side effects, error behavior, or whether an existing session is required.

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?

One sentence with no filler, and the most important information ('stored diagnostic summary plus every diagnostic attempt') comes first. It is appropriately sized for a simple getter.

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?

The description states what is returned (summary plus all attempts), which is helpful because there is no output schema. However, it omits any prerequisite or error context and provides no output structure, so an agent has only a minimal picture for a tool with no annotations.

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?

The schema has one parameter (session_id) with 0% description coverage, and the description does not mention session_id at all. The parameter's role is inferable from its name, but the description adds no meaning about how the session is used or what makes a valid session.

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 ('Return') and names a precise resource: the stored diagnostic summary plus every diagnostic attempt. It is clear about what is being retrieved, though it doesn't explicitly contrast with sibling diagnostic tools such as generate_diagnostic or get_assessment_history.

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 guidance is given about when to call this tool instead of sibling getters like get_review_state or get_assessment_history. The word 'stored' hints that it should be used after a diagnostic has been saved, but this is not made explicit and no exclusions are provided.

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