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

The description goes beyond the annotations by stating 'Pure static text — no engine call, deterministic output' and disclosing limitations such as single deterministic replication, cached results, warm-up inside the reported window, and fixed sample parameters. This gives the agent confidence about side effects and determinism beyond the readOnly/idempotent hints.

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 longer than typical, but it front-loads the core purpose and usage rule before diving into content details. Most of the detail is necessary to communicate what the reference text covers, though some clauses could be tightened without losing 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?

With no parameters, an output schema present, and rich annotations covering read-only and idempotent behavior, the description fully covers the remaining context: purpose, content scope, usage conditions, alternatives, and limitations. Nothing essential is missing for an agent to select and call this 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 input schema has zero parameters and schema description coverage is 100%, so there are no parameter semantics to clarify. The description appropriately focuses on content and behavior rather than parameters, meeting the baseline for a parameterless tool.

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 identifies the tool as a reference text explaining how the supply-chain simulation works, and distinguishes it from run_simulation by noting it produces no engine call and static output. It is specific about the resource and the topics it covers, so an agent can tell it apart from the other explain/reference siblings.

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 explicitly states when to use this tool: when the user asks conceptual 'how does it work', 'why did this DC stock out', or 'should I simulate or optimize' questions, rather than asking for a number. It also names the alternative tool, run_simulation, for when actual figures are requested.

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