agy_result

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

Without annotations, the description carries full burden. It states the tool returns a 'completed planner response and terminal status,' implying a read-only operation. However, it does not disclose behavior for invalid run_ids, error states, or whether results are cached. Annotations could fill gaps, but none are provided.

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?

The description is a single sentence, making it concise. However, it lacks structure such as bullet points or additional context that could improve readability for an agent.

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?

Given the 1 required parameter and no annotations, the description is barely adequate. It does not explain what 'planner response' or 'terminal status' mean, nor does it clarify that only completed runs are valid. The existing output schema partially compensates for return value description, but the lack of usage context and parameter documentation leaves gaps.

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 only parameter, 'run_id', has no description in the schema (0% schema_description_coverage) and the tool description does not explain its meaning, format, or how to obtain it. This leaves the agent unable to correctly specify the parameter without external knowledge.

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 clearly states it returns 'the latest completed planner response and terminal status,' specifying both the verb (Return) and the resource. It differentiates from siblings like 'agy_status' (which likely returns just status) and 'agy_transcript' (which likely returns a transcript) by combining both elements.

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 description offers no guidance on when to use this tool versus alternatives such as 'agy_status' or 'agy_transcript'. It does not mention prerequisites (e.g., planner must have completed) or conditions that would make this tool inappropriate.

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