badgr_down

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

No annotations are provided, so the description carries the full burden. "Terminate" implies a destructive, likely irreversible action, but the description never says whether data/volumes are lost, whether shutdown is graceful, whether billing stops immediately, or how a missing/already-terminated deployment is handled.

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?

One short sentence with the action and its effect front-loaded; zero filler. The only issue is that more content would have been justified, not that anything is 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?

For a single-parameter tool with no output schema this is minimally sufficient to invoke correctly, but for an unannotated destructive operation the description should disclose irreversibility and any data-loss semantics, which it does not.

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 100% and the single parameter is documented as "Deployment ID to terminate," so the baseline of 3 applies. The description adds nothing about ID format or how to obtain a valid deployment_id.

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?

Specific verb ("Terminate") plus specific resource ("a Badgr deployment") and an explicit outcome ("stop billing"). It is clearly the teardown counterpart to badgr_run/badgr_serve, though it never names those siblings directly.

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 guidance on when to call this versus badgr_status or badgr_run, no prerequisites, and no exclusions. The agent must infer that this is the stop/decommission operation and that it should only be used on a deployment that should no longer exist.

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