demo_orders

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

Annotations already cover readOnly, idempotent, and closed-world, so safety is documented. The description adds genuine behavioral context beyond that: nothing is fetched or stored, and output is deterministic (same limit → same records, larger limit → more repetition). It stops short of describing record fields, but that is minor.

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-loaded with the core behavior and the sibling pointer early. Slightly wordy in the middle clause about 'what terse does,' but every sentence carries usable information and nothing is padded.

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 output schema, the description must carry the return-format burden, and it does by noting a JSON record array plus determinism and the limit-driven count. Adequate for a simple one-param demo tool; record internals are left unspecified but are arguably out of scope.

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 100% with one param, so the baseline is 3. The description goes beyond the schema by explaining the effect of the limit value on output volume and repetition, adding meaning the schema's '1-40' range does not convey.

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 verb and resource ('Return a synthetic order book as a JSON record array') and explicitly distinguishes itself from its only sibling ('For the non-JSON counterpart, use demo_logs'). An agent can immediately tell what this produces and how it differs from demo_logs.

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?

Names the alternative (demo_logs) and the condition that selects it (non-JSON counterpart), and clarifies the intent ('the point is the shape, so you can see what terse does to a record-shaped tool result'). Both when-to-use and the alternate are explicit.

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