execute-runbook

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

With no annotations provided, the description carries the full burden. It discloses the fire-and-forget vs synchronous modes, which is some behavioral context, but it does not reveal side effects (e.g., creating an execution record, triggering actions), permission requirements, reversibility, or what happens on failure. This is insufficient for an execution/mutation tool.

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, efficient sentence with no wasted words. It is front-loaded with the action and includes the key mode distinction. However, it is slightly under-specified given the tool's complexity, so it does not earn a perfect conciseness score.

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?

This is a mutation tool with no annotations, no output schema, and incomplete parameter coverage. The description lacks any mention of return values, side effects, prerequisites, or how the sync/async modes affect the response. It is minimally viable but leaves significant gaps for an AI agent to use it 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 covers runbook_id (no description) and execution (generic 'payload...' description), giving 50% coverage. The tool description adds no parameter semantics. It does not explain what the execution object should contain or how runbook_id relates to the runbook resource, failing to compensate for the schema's gaps.

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 executes a runbook, using a specific verb and resource. The parenthetical '(fire-and-forget or synchronous)' adds execution modes, distinguishing it from runbook management siblings like get-runbook-executions or update-runbook-execution.

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?

There is no guidance on when to use this tool versus alternatives, nor any prerequisites or exclusions. The sync/async choice is mentioned but not elaborated, leaving the agent without information on selecting the appropriate mode or when to prefer other runbook operations.

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