delete_hybrid_deployment_agent

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

With no annotations, the description must disclose behavioral traits. It warns 'DESTRUCTIVE' but does not explain what is destroyed (e.g., agent, configurations), whether the action is reversible, or required permissions. The warning adds some transparency but is insufficient for full burden.

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 consists of two short sentences, front-loading the warning with an emoji. Every part is essential and no words are wasted.

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 tool's destructive nature and lack of output schema, the description covers the critical need for user confirmation and a safety mechanism. It could mention permanence or error cases, but the warning and confirmation instruction are sufficient for a single-action delete 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?

Schema coverage is 100%, and the description adds extra meaning for the schema_file parameter by requiring the user to first read a specific schema file and provide its path as confirmation. This goes beyond the schema's type/description.

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 'Delete a Hybrid Deployment Agent' with a specific verb and resource. It distinguishes itself from sibling tools like create_hybrid_deployment_agent and get_hybrid_deployment_agent by focusing on deletion.

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 includes a prominent warning '⚠️ DESTRUCTIVE - Confirm with user before calling,' which provides clear guidance on when to use (only after user confirmation) and implies it should not be used without caution. However, it does not explicitly exclude alternative tools.

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