ops_playbook_run

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

With no annotations, the description carries the full disclosure burden. It mentions 'config-backed defaults' (explains parameter optionality) and 'state persistence' (hints at side effects). However, it fails to clarify the tool's safety profile (destructive vs safe), authentication requirements, or what 'running' actually entails (sending messages? creating tickets?).

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?

Single dense sentence with no filler. Front-loaded with the core action. Information-to-word ratio is high. However, extreme brevity may hinder comprehension given the tool's complexity (15 parameters), though this is primarily a completeness issue rather than conciseness failure.

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?

Inadequate for a complex 15-parameter operational tool with no output schema and zero annotations. Missing: parameter-to-playbook mappings, return value description, error handling behavior, and safety warnings expected for incident management workflows. The 'config-backed defaults' hint is insufficient operational guidance.

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?

Schema description coverage is 0%, requiring the description to compensate significantly. It fails to do so, providing no explanation for 15 parameters including critical distinctions like 'channel' vs 'channels', the purpose of 'dry_run', or which parameters apply to which playbooks. The parenthetical playbook names merely repeat the schema enum.

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 (Run) and resource (operations playbook) with specific parenthetical examples (incident open, support digest, release broadcast). It distinguishes from ops_playbook_list by emphasizing execution over listing. However, it doesn't explicitly differentiate from direct action siblings like ops_incident_create or ops_broadcast_message.

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 explicit guidance on when to use this tool versus alternatives like ops_incident_create or ops_broadcast_message. The examples imply use cases but don't clarify selection criteria or prerequisites (e.g., which playbook to choose, required vs optional parameters with config defaults).

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