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

Beyond the readOnlyHint annotation, the description adds meaningful behavioral context: it names the source (Pinnacle), the time buffer, the returned concepts (drop percentage and nvp), and explicitly cautions that nvp is an estimate and that the signal does not prove informed money. This helps the agent set expectations without needing to call the tool.

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 dense but every clause contributes meaning: the core purpose is front-loaded, the nvp definition is justified by its use cases, and the limitations are stated explicitly. No filler or redundant restatement of the tool name exists.

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 there is no output schema, the description does a good job naming the expected returned fields: from/to decimal prices, drop %, and nvp. It also provides the time buffer and caveats. A minor gap is that the exact output shape, ordering, or grouping of records is not specified, but this is not critical for selecting and invoking the tool.

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 100%, so all four parameters are already documented. The description adds broader context around drops and nvp, but it does not add parameter-specific semantics beyond what the schema provides. This matches the baseline for a fully covered 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 identifies the tool as returning recent Pinnacle price drops, with an explicit definition of what counts as a drop: outcomes whose odds shortened. It is readily distinguishable from sibling tools like get_live_odds or get_prematch_lines because it focuses specifically on drops/steam moves rather than general odds.

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 conveys when the data is useful (recent Pinnacle drops, roughly last 3 hours) and what it cannot do (does not compare sportsbooks or prove informed money). However, it never explicitly tells the agent when to prefer this tool over siblings such as get_live_odds or get_prematch_odds, leaving the choice to inference.

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