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

With no annotations, the description carries the full burden of behavioral disclosure. It goes beyond a bare statement by revealing that the operation is public, requires no API key, and what the coverage gates actually measure. It does not mention rate limits or detailed response behavior, but the output schema fills part of that gap.

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 compact, front-loaded with the primary purpose, and every sentence contributes useful context: what the tool returns, access requirements, and what the coverage gates mean. There is no fluff or repetition.

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 simple public read operation with an output schema and optional parameters, the description provides adequate high-level context. However, it falls short on parameter semantics and does not explicitly guide the agent on when to use this tool versus related siblings like source_quality.

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 coverage is 0%, so the description must compensate for the undocumented parameters include_warn and window_minutes. It does not explain either parameter; the closest hint is that 'freshness' checks relate to a time window, but no concrete mapping is provided.

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 opens with a specific verb and resource: 'Return public per-book coverage gates.' It then adds what those gates represent—whether sources survive freshness, normalization, database, REST-shape, and stream-shape checks—which distinguishes it from sibling tools like parlayapi_source_quality or odds-related 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?

It clearly states 'No API key required' and that the data is public, which helps an agent know access is unauthenticated. However, it does not explicitly say when to prefer this tool over alternatives or when not to use it, so the usage guidance is mostly implied rather than stated.

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