throttling

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

No annotations provided, so description carries full burden. It fails to disclose whether changes apply immediately to active connections, persist across sessions, or explain behavioral differences between enum values like 'off' vs 'deactivate' vs 'stop'.

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?

Single sentence, appropriately front-loaded with zero redundancy. Every word earns its place.

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 low complexity (1 parameter), 100% schema coverage, and existence of output schema, the description is minimally viable. However, lacks behavioral context that would help an agent distinguish between the 'off'/'deactivate'/'stop' states.

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%, documenting the preset parameter and its allowed values. The description adds no parameter semantics, earning the baseline score for high schema coverage.

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 uses a specific verb ('Set') and clear resource ('network throttling preset'), distinguishing it from sibling analysis/capture tools. However, it assumes familiarity with 'Charles' (Charles Proxy) without context.

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 provided on when to apply throttling vs. analyzing traffic, prerequisites (e.g., active capture session), or how to disable throttling (though 'off'/'deactivate' enum values exist).

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