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

Beyond the readOnlyHint annotation, the description adds that the complete list is free, requires no key or email, and covers standard, half-PPR, and full-PPR formats. This gives useful access and scope context, although it does not mention rate limits or output formatting.

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 main function and key differentiators are front-loaded, with the free-access note and example searches following logically. The list of five example queries is slightly repetitive but each example adds value for intent matching, so the overall structure is efficient.

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?

For a zero-parameter, read-only list tool with no output schema, the description covers the model context, scoring formats, filter concept, access requirements, and example user intents. It is missing explicit details about the returned fields, but this is a minor gap given the tool's simplicity.

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 properties, so the baseline is 4, but the description claims 'Filter by position or draft round' without any corresponding parameters. This is misleading: an agent following the schema cannot pass these filters, creating a contradiction between the described capability and 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 the tool identifies the biggest gaps between the PredictionMarketsPicks model and consensus ADP for 2026, differentiating sleepers and busts. It is specific about the resource and output, and the context of fantasy football and draft cost distinguishes it from sibling tools like adp_market_gaps or compare_players.

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 provides explicit example search intents—'fantasy sleepers 2026', 'draft busts to avoid', 'undervalued players'—which tells an agent when to use this tool. It does not list exclusions or name alternatives, but the use cases are clear enough for routing.

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