get-runbook-executions

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

With no annotations, the description carries the full burden of behavioral disclosure. 'Get all executions' implies a read operation but does not disclose pagination, ordering, return format, or whether the result is a list or summary. The agent knows it is a getter but lacks detail about side effects or data shape.

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?

A single sentence that efficiently conveys the core purpose with no filler. Every word earns its place.

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 existence of sibling tools like get-runbook-execution, update-runbook-execution, and delete-runbook-execution, the description lacks guidance on relationship to those tools. It also does not explain what an 'execution' is, how many results to expect, or whether pagination exists. With no output schema, the description leaves significant gaps for a simple list tool.

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 defines runbook_id as a string, and the description mentions 'for a runbook', which connects the parameter to the resource. However, it adds no additional semantics beyond what the schema already conveys. With a single self-explanatory parameter, this is adequate but not rich.

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 action ('get all'), the resource ('executions'), and the scope ('for a runbook'). This distinguishes it from the sibling tool get-runbook-execution, which retrieves a single execution. The verb + resource + scope 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?

No guidance is provided about when to use this tool versus alternatives. There is no mention that get-runbook-execution should be used for single execution retrieval, nor any exclusions or prerequisites. The description merely states what it does, leaving the agent to infer usage context.

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