sort_table

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

Describes sorting direction, header preservation, and missing cell handling. Missing details on in-place modification, error cases (e.g., invalid index), and impact on document state. Annotations absent, so burden is on description.

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?

Description is concise, front-loaded with key behavior, and uses a clear Args/Returns structure. Could be marginally more structured but effective.

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?

With output schema present and simple parameters, description covers sorting logic, header handling, and missing cells. Minor gap on error handling and side effects.

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 0%, so description compensates by explaining each parameter's meaning (e.g., 0-based index, default ascending). Adds value beyond the raw schema.

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?

Clearly states the tool sorts non-header rows by column text. Header row behavior and missing cell handling are specified, distinguishing it from other table 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?

Implied use for sorting table rows, but no explicit guidance on when not to use or alternatives. Among siblings, this is the only sort tool, but lacking context for proper selection.

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