stop_all_services

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

With no annotations provided, the description discloses the tool's bulk stopping behavior and return value (request info or error message). However, it does not mention the destructive nature (all services stopped), whether it requires confirmation, or any prerequisites like cluster state. This leaves some behavioral gaps.

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 structured with clear sections (role, core functions, usage scenarios) and is front-loaded with purpose. Some phrases are slightly redundant (e.g., 'Dedicated tool' and 'bulk stopping'), but overall it is concise and well-organized.

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 has no parameters and an output schema (likely documented elsewhere), the description covers the core behavior, return value, and usage scenarios. It doesn't mention limitations or side effects beyond what is implied, but for a simple action tool, it is sufficiently complete.

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 tool has zero parameters, and the input schema is empty with 100% coverage. The description does not need to add parameter meaning, and it properly avoids mentioning non-existent parameters. Baseline 4 is appropriate.

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 stops all services in an Ambari cluster, using the exact phrase 'Stop All' from the Ambari Web UI. It distinctively sets this tool apart from siblings like 'stop_service' (single service) and 'start_all_services' (opposite action).

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 explicitly lists required usage scenarios like 'stop all services', 'stop everything', and 'cluster shutdown', making it clear when to use. It does not explicitly exclude other scenarios, but the context implies it should not be used for stopping individual services.

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