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

Annotations only declare destructiveHint=true; the description adds real behavioral context beyond that: inference halts, GPU billing stops accruing, and the parenthetical "(pause)" signals the operation is a reversible suspension rather than a deletion. It still doesn't say whether the call is idempotent on an already-stopped deployment or what happens to queued work.

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?

Three short, front-loaded sentences: purpose first, consequence second, transport detail last. Nothing is padding and the most decision-relevant information (billing stops) appears immediately.

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, non-returning mutation with destructiveHint already set, the description covers purpose, effect, and endpoint. No output schema exists, so return values need not be explained; only idempotency/state-after-stop is a remaining gap.

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 deploy_id parameter is already documented as required with a meaning-carrying description. The description adds no syntax, format, or sourcing guidance beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource ("Stop (pause) a running dedicated deployment") and immediately scopes what that means. It is clearly distinguishable from sibling tools like deepinfra_start_deployment and deepinfra_get_deployment without opening any schema.

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?

Usage is implied by the effect (halting inference and stopping GPU charges), which tells the agent why one would call it, but it never names the alternative (deepinfra_start_deployment) or states preconditions/exclusions. Adequate but the agent must infer the lifecycle pairing itself.

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