simulate_load

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false), and the description usefully clarifies that this is a simulation producing comparative metrics per guard rather than a real-traffic operation. It does not say anything about cost, runtime, or whether the simulation is deterministic given the seed — and it repeats return fields that the output schema already documents.

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?

Front-loads the core purpose in one sentence, then attaches parameter and return notes compactly; no filler sentences. The awkward line breaks and the phrase "'check everything'" in quotes, which is never defined, cost a little clarity.

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?

An output schema exists, so declining to explain the returned metrics in detail is acceptable. But with five undocumented parameters and a jargon term ('check everything', 'deadline-aware guard') that is never defined relative to the sibling tools, an agent cannot confidently set load, seconds, or deadline_ms without guessing.

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 0% across five parameters, so the description carries the burden and only partially meets it: it enumerates the three valid traffic values ('steady', 'rush_hour', 'real_chatbot' with WildChat timings), which is genuinely useful since the schema has no enum. Load, seed, seconds, and deadline_ms are entirely undefined — no units, ranges, or effect on the simulation.

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 action: race a 'check everything' strategy against a 'deadline-aware guard' with measured check costs, which together with the name simulate_load makes clear this is a load/stress simulation. It does not explicitly distinguish itself from siblings like check_message or decision_matrix, so an agent must infer that this is the offline simulation counterpart to live checking.

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 explicit when-to-use or when-not-to-use statement, and no mention of prerequisites or alternatives. Usage is implied by the word 'simulate' and by the traffic-mode list, from which an agent can infer this is for pre-deployment capacity testing rather than live message checking, but the routing decision against check_message is left to inference.

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