xlsx_sort

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

Beyond annotations (readOnly, idempotent), description adds stability across sort keys, type-aware comparison, and nulls sorting last. This enriches understanding of tool behavior beyond safety/cache hints.

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?

Concise but informative: first line defines core functionality, then behavioral details, then usage guidelines. No wasted words.

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?

Covers core purpose, usage, and behavioral traits. Lacks details on error handling or file format constraints, but given good annotations and simple nature, it's fairly complete. Mentions return format (markdown table).

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 0%. Description only explains the 'by' parameter (multi-column, direction) but doesn't clarify 'file_b64' (file input) or 'options' (header_row, limit, sheet). Missing important parameter context.

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?

Description clearly states it sorts rows of a local .xlsx file with multi-column and per-column direction. It uses specific verb 'sort' and resource 'xlsx file', and distinguishes from siblings by focusing on sorting rather than other data operations.

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?

Explicit USE WHEN and DO NOT USE WHEN sections with alternative tool (xlsx_read) for cases where data is already sorted or for upload/attached files. Provides clear decision criteria.

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