set_throttling

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

Discloses auto-cleanup behavior and provides a comprehensive list of presets. Without annotations, the description carries the full burden and does well, though it could mention potential impact on other operations.

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 bullet points, clear sections, and no redundant information. It is concise yet fully informative.

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?

Covers usage, parameters, and behavior well. Although output schema exists but not described, the tool's action is simple (toggle throttling), so the description 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?

Schema coverage is 0%, but the description explains the preset parameter thoroughly: valid values are preset names or null, and all preset names are listed. The compensation is complete.

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 it switches network bandwidth throttling, with preset enabling and null disabling. It distinguishes itself from sibling tools which are all filtering or data-related.

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 describes when to use preset vs null, and mentions auto-cleanup on process exit. No need to specify alternatives as siblings are unrelated.

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