emulate_cpu

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

With no annotations, the description carries full burden. It explains the behavioral effect of rate values and that setting rate=1 resets the throttle. It does not discuss potential side effects or permissions, but for a simple emulation tool, this is sufficient.

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 two well-structured sentences. The first sentence states the action and mechanism. The second sentence explains rate values. No redundant words; every part adds value.

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 the tool's simplicity (single parameter, no required params, output schema exists), the description is complete. It covers all necessary information for an agent to select and invoke the tool correctly.

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?

The schema has 0% coverage and only provides type and default. The description adds critical semantics: meaning of rate=1 (no throttle), rate=4 (4x slowdown), rate=6 (low-end mobile), and that 1 resets. This fully compensates for the lack of schema description.

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 the tool throttles CPU via CDP Emulation.setCPUThrottlingRate. It provides explicit rate values and their effects, distinguishing it from other emulation tools. The verb 'Throttle' and resource 'CPU' are specific.

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?

The description gives clear usage context by mapping rate values to real-world scenarios (DevTools default, low-end mobile, reset). It does not explicitly mention when not to use, but the single-parameter nature and lack of sibling CPU tools make usage straightforward.

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