get-runbook-execution

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'get', which implies a read operation, but it does not state whether it is read-only, what it returns, possible errors, or any permissions required. This is minimal transparency for a tool with no annotation support.

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, clear sentence with no fluff. It is concise and to the point, which is appropriate for a simple getter tool.

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?

There is no output schema, no annotations, and the description does not explain what a 'runbook execution' object contains or what the response looks like. While the tool is simple, the description leaves important context gaps, especially for an agent that needs to use the returned data correctly.

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 provides no descriptions (0% coverage), and the description only mentions 'instance ID' as the identifier. The runbook_id parameter is not explained at all, leaving the agent to guess its role. The description adds partial meaning but does not compensate for the schema's lack of descriptions.

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 the tool gets a specific runbook execution, with the qualifier 'specific' and 'by instance ID'. This distinguishes it from the sibling tool get-runbook-executions, which presumably lists executions. The verb and resource are specific and unambiguous.

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 word 'specific' implies this is for retrieving a single execution rather than listing all, but it does not explicitly mention alternatives like get-runbook-executions or explain when to use this tool vs. others. The guidance is implied rather than stated.

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