get_execution_result

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

With no annotations, the description carries the burden of behavioral disclosure. It clearly discloses a meaningful access-control trait: only the originating session can read the result. This goes beyond what the schema or name conveys. It does not mention other behaviors like result retention or errors, but given the output schema covers return format, this is decent.

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 sentences, front-loaded with the core purpose, and every word adds value. The security constraint is essential and concisely stated.

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 simple retrieval tool with an output schema and 2 self-explanatory parameters, the description provides the essential context: what it retrieves and who can access it. It lacks error-condition details, but these are secondary given the output schema. It is reasonably complete for its complexity.

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 input schema has 2 parameters with 0% description coverage. The description does not directly explain the purpose or format of session_id and execution_id, though the sentence about session access hints at session_id's role. It fails to compensate for the schema's lack of parameter documentation.

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 ('Retrieve') with a clear resource ('stored execution result'), and the 'stored' qualifier distinguishes this from execute_capability, which likely runs an execution. The purpose is immediately obvious.

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 implies this should be used after an execution has been stored and when you need to fetch that result, but it does not explicitly name alternatives (e.g., execute_capability) or provide when/when-not guidance. The session restriction is a usage constraint but not a usage guideline.

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