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

With no annotations, the description carries the full behavioral burden. It usefully discloses case-insensitive matching and a 50-row result cap, but is silent on result ordering, default limit behavior, and whether this is a pure read with no side effects — though 'up to 50' partially duplicates the schema maximum.

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?

A single tight sentence with the resource, matching semantics, and cap front-loaded; no filler. It reads as a sentence fragment, but nothing is wasted.

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 2-parameter search tool with no annotations and no output schema, the description covers matching semantics and result count but omits ordering, default limit, and what a returned row looks like. Adequate minimum, with clear gaps.

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 coverage is 50%: query is documented, limit is not. The description adds real meaning for query by specifying 'any cell' plus case-insensitivity, and clarifies limit's upper bound, but provides no default value or guidance on choosing a limit, leaving the undocumented parameter only half compensated.

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?

States a specific verb+resource (rows of the Fair Odds Calculator dataset) and the matching scope (cells containing the query). It clearly distinguishes itself from a stats/compare tool, but never names or contrasts with siblings like dataset_row or dataset_top, so an agent must infer that this is the free-text entry point.

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?

No when-to-use guidance, prerequisites, or exclusions are given. The description implies a free-text substring search, but nothing tells the agent when to prefer this over dataset_row or dataset_top, or what to do when no rows match.

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