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

Annotations already establish readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds real context beyond that: results are scored by FloorFeed against its own floor history, status is surfaced, and leaderboard entries require 5+ settled calls. It omits nothing critical for a read-only query, though ranking/limit behavior is unstated.

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?

Three tight sentences: what the data is, then the two modes in parallel structure. The clipped 'With a symbol… Without…' phrasing is efficient rather than confusing, and the core definition is front-loaded with zero filler.

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-required-param read tool with annotations covering safety and no output schema, the description supplies the data's meaning, scoring basis, and mode behavior. Only the leaderboard size and per-call status vocabulary are missing, which is minor.

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 100%, so the baseline is 3. The description goes further by explaining the semantic consequence of the optional symbol parameter — supplying it switches from a per-collection call list to a caller leaderboard ranked by hit rate — which the schema's short text does not convey.

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 and resource: members' public floor-price calls, scored against FloorFeed floor history. It distinguishes the two operating modes (per-symbol vs leaderboard). It does not name the obvious sibling (my_calls) to contrast public calls with the caller's own, which would have made the split explicit.

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 'With a symbol / Without' framing tells the agent how the two modes differ, which implicitly signals when to use each. However, it never names an alternative tool or states when NOT to use this one (e.g. use my_calls for your own calls), so routing to the right sibling is left to inference.

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