emergency

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

The description discloses high-impact destructive behavior and the need for explicit confirmation. It explains the preview-then-confirm workflow. Annotations only have openWorldHint, so the description carries the burden and does so thoroughly, without contradiction.

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 concise (3 sentences) and front-loaded with the purpose. Every sentence adds essential guidance without redundancy. It efficiently covers purpose, usage pattern, and special behavior.

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?

The description covers the main actions and workflow. Given the complex oneOf schema with multiple actions and the presence of an output schema, the description provides sufficient context for an agent to use the tool correctly, though it could briefly mention the output preview behavior.

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 coverage is 100% with parameter descriptions, so the description doesn't need to repeat them. However, it adds semantic meaning by explaining the workflow (preview without confirm, then confirm) and the wait parameter's human-ask requirement, going beyond the schema's basic 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's purpose as 'Emergency and bulk operations' and lists the specific actions (stop_all, redeploy_project, restart_project). It distinguishes itself from sibling tools by emphasizing high-impact destructive actions, which implies it is for urgent or bulk scenarios unlike sibling tools like 'database' or 'project'.

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 provides explicit usage guidelines: call without confirm first to preview effects, ask the human before retrying with confirm, and always ask before setting wait:true on redeploy_project. This tells when and how to use the tool, and when not to directly execute.

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