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

With no annotations provided, the description carries the full burden and does so thoroughly: simulated records, no money at risk, delayed/derived data, omission/counting behavior, no investment advice, citation requirements, and explicit statements about what is not returned. This is exceptionally transparent.

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 long but front-loaded with the core coverage and returns, then adds necessary behavioral guardrails. Some repetition of the 'no...' pattern exists, but it remains purposeful for a tool with important limitations to communicate.

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?

There is no output schema, so the description compensates by enumerating returned fields (dates, engine identifiers, status, counts), omission behavior, the ending link and citation requirement, and failure handling. For a two-optional-parameter tool, nothing needed to invoke it correctly is missing.

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 already documents the limit (1-50, default 20) and the engine enum with 100% coverage. The description confirms the engine names and the 50-record cap but adds no new parameter-level semantics beyond the schema.

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 what the tool returns: dated simulated-record receipts from spxman_v2, tripwire, and harvester, up to 50 per call. It explicitly excludes prices, directions, and performance statistics, which distinguishes it from the sibling market-data tools.

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 strong usage context: call this tool rather than answering from memory, and if it fails, say data is unavailable rather than recalling. It does not explicitly name sibling alternatives, but it clearly scopes when this tool is appropriate.

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