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

Discloses that it is 'PAID $0.02' and indicates data source ('from the fleet's live cross-venue liquidation observation'). It does not explicitly state read-only or side-effect-free behavior, but the analytics nature and payment note are transparent enough.

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?

Description is moderately concise but includes redundant phrasing like 'where it's crowded vs where there's room to win' and 'From the fleet's live cross-venue liquidation observation' which could be trimmed without losing meaning.

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?

Provides sufficient context for the tool's purpose, payment requirement, and the kind of output (concentration, top share, verdict). Without an output schema, this is enough for an agent to know what to expect, though an example or more specific output format would improve completeness.

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 covers the single parameter thoroughly, including encoding, purpose, and usage flow. The tool description adds no additional parameter context, so baseline 3 applies for high schema coverage.

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?

Clearly states it provides liquidator competition analytics, listing specific metrics (concentration, top-liquidator share, per-venue verdict) and the goal ('where it's crowded vs where there's room to win'). This distinguishes it from siblings like farm_liquidations or farm_mesh.

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?

Does not explicitly state when to use this tool versus alternatives. The description focuses on what it does but provides no guidance on conditions that would make this tool preferable over, say, farm_liquidations or farm_summary.

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