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

With no annotations, the description carries the full behavioral burden, yet it only restates that it ranks rows. It does not disclose direction defaults beyond the schema, tie-breaking behavior, the 1-50 limit cap, return format, or any access/permission requirements. This leaves substantial behavioral gaps for a ranking 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?

A single front-loaded sentence that leads with the operation and follows with a short clarifying gloss. Efficient, with no wasted clauses, though the gloss is somewhat redundant with the opening clause.

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 three-parameter read tool with no output schema and no annotations, the description is minimally adequate: it explains the core ranking concept but omits tie handling, the limit bound, and any sense of the returned shape or ordering guarantees.

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 only 33% (ascending is documented in the schema), so the description should compensate but largely does not. It conveys that 'column' must be numeric but omits that 'column' is required, the meaning of 'limit', and the 1-50 bound, adding little beyond the schema text.

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 states a specific operation (return the highest/lowest rows by a numeric column) against a named resource (the Excurvo dataset), with the gloss "which is the most/least X" making the intent concrete. It does not, however, distinguish itself from siblings like dataset_stats or dataset_row, which could also surface extremes or single rows.

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 phrasing "which is the most/least X" implies the use case (finding extremes) but never states when to prefer this over dataset_stats, dataset_search, or dataset_row, nor any prerequisites. Usage is implied rather than guided.

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