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

With no annotations, the description carries the full burden. It mentions ranking by a numeric column but does not disclose the limit parameter's role, default ordering, whether the operation is read-only, or the output format. The phrase 'highest (or lowest) rows' hints at sorting but omits key behavioral details.

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 a single, concise sentence with the core action front-loaded. The appended phrase 'which is the most/least X' is slightly redundant but not harmful. It is appropriately sized.

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 simple read tool, the description lacks essential details such as how 'limit' affects the result and what the output looks like (full rows? subset of columns?). Without an output schema, the agent must infer the return structure. The description does not mention default ordering or error cases, making it incomplete.

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?

The description adds that the column must be numeric, which is helpful, but it does not explain the 'limit' parameter (number of rows to return) or the default behavior of 'ascending'. With only 33% schema coverage, the description should compensate for the undocumented 'column' and 'limit' parameters, but only partially does.

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 states the tool ranks rows by a numeric column, identifying the resource (TakeoffDeck dataset) and the action (return highest/lowest rows). It is distinct from sibling tools like dataset_search, dataset_stats, etc., which serve different purposes.

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 a use case ('which is the most/least X') but does not explicitly mention when to choose this over alternatives like dataset_search or dataset_stats. There is no guidance on when not to use it or what conditions make it appropriate.

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