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

With no annotations, the description carries the full burden and does disclose cost per call, authentication options, excluded raw fields, and the educational nature of the data. It does not explicitly state whether the tool is read-only or whether repeated calls incur multiple charges, but the payment and auth details are 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 longer than necessary and mixes payment instructions, data source explanations, and disclaimers into one block. It contains useful information, but the repeated payment flow and catalog promotion could be trimmed for clarity.

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?

The description lists returned fields, sorting order, limit behavior, and payment requirements, which covers a lot without an output schema. However, it does not describe the actual response structure, possible absence of data, or error conditions such as payment failure.

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 only parameter, limit, is described in the schema with a default, and the description adds the cap of 50 and clarifies it is optional. This is sufficient for the single parameter, though no other parameters exist.

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 that the tool returns player prop edges with specific fields like edge_pct, fair_prob, and direction, which makes the primary purpose identifiable. However, the odd phrase 'News Gurus Intel' and the lack of an explicit 'gets sports props' action slightly obscure clarity.

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 explains how to pay and that results are sorted by edge_pct, but it gives no guidance on when to prefer this tool over the many sibling tools. There are no usage alternatives or contextual cues such as 'use this for X, not for Y.'

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