Reboot the modem behind a proxy

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

Annotations already declare destructiveHint=true and idempotentHint=false, but the description adds concrete consequences beyond them: active connections drop, recovery takes about a minute, and it is rate-limited to once per 30 minutes per proxy. That rate limit is operationally critical and appears nowhere in structured fields.

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 sentences, zero filler, and the highest-value facts (what it does, when to use it, blast radius and duration) are front-loaded in that order.

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 one-parameter destructive operation with no output schema, the description covers purpose, side effects, downtime, and rate limit — everything an agent needs to decide and warn before calling.

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?

Only one parameter, and the schema already carries a 100% description ("Mobile proxy_id from list_proxies"). The description adds no parameter-level detail, but with a single fully-documented identifier the baseline of 4 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+resource ("Power-cycles the 4G modem behind a mobile proxy") and immediately frames it against the sibling it is not — rotate_ip. An agent can distinguish this from rotate_ip or restart-style siblings without opening the 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?

Explicitly defines the trigger condition ("hangs where the proxy stops passing traffic") and the exclusion ("rotate_ip does not help"), naming the alternative by name. When-to-use and when-this-is-the-right-escalation are both stated.

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