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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'highest (or lowest) rows' and does not mention default limits, tie handling, handling of non-numeric or missing values, output format, or performance implications.

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 short and front-loaded with the core purpose, and every phrase contributes to identifying the operation. It is slightly redundant with the title, but the added dataset name and the 'most/least X' framing provide useful specificity.

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 tool with only three parameters and no output schema or annotations, the description is minimally adequate: it names the dataset, the ordering basis, and the high/low choice. However, it lacks details about default limit values, output shape, and edge-case behavior, which an agent might need when 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 only 33% (only the ascending parameter has a schema description). The description compensates somewhat by specifying that the column must be numeric and by linking ascending to 'lowest first' versus 'highest first', but it leaves the 'limit' parameter's meaning and default behavior unexplained.

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 title 'Rank rows by a numeric column' and the description together clearly state that the tool returns the highest or lowest rows of a specific dataset by a numeric column. It names the resource (BurdenRateLedger) and the ordering concept, though it does not explicitly contrast itself with sibling tools.

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 implies when to use it ('which is the most/least X'), but it gives no explicit guidance on when to choose this tool over sibling tools like dataset_search or dataset_stats. There are no exclusions, alternative references, or use-case boundaries beyond the general 'top/bottom rows' idea.

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