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

With no annotations, the description carries the burden and does so excellently. It discloses that totals include the operator's own seed-agent trades and verification runs, and that the organic split is stated separately. It also warns about potentially misleading demand reporting—valuable behavioral context beyond basic read-only/write labeling.

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 moderately sized and largely front-loaded with the key output categories, but the final sentence ('A marketplace that reports its own seeding...') is rhetorical and does not help an agent select or invoke the tool. Somewhat over-written for a zero-parameter tool.

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 output schema exists and there are no parameters, the description sufficiently conveys what data the tool returns and how to interpret it. However, it omits explicit usage context relative to siblings, which prevents a perfect score.

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 tool has zero parameters, so the baseline is 4. The description appropriately focuses on what the stats contain rather than parameter syntax, which is irrelevant here.

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's resource (market statistics: published indexes, recent trade tape, windowed volume) and conveys that it provides aggregate venue numbers. It lacks an explicit verb like 'get' or 'list', and does not directly contrast with sibling tools, so it falls short of a 5.

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 when-to-use or alternative guidance is provided. The only instruction is to 'Read the organic figures, not the totals,' which is interpretive advice for the output, not guidance on selecting this tool over siblings like standing_demand or search_solved.

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