sort_range

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

Without annotations, the description carries full burden. It does not disclose that sorting is an in-place mutation, potential side effects (e.g., changes to formulas or formatting), or required permissions. The description is minimal.

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 sentence, highly concise. However, it sacrifices informational content for brevity, making it borderline under-informative.

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?

Given the complexity of sorting in Sheets (multiple sort specs, possible data types), the description lacks completeness. No output schema, no annotations, and the description does not mention return values, error conditions, or limitations.

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 must compensate. It mentions SortSpec objects but does not explain their structure or how to construct them. The sort_specs parameter is an array of objects with additionalProperties: true, leaving ambiguity that the description does not resolve.

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 it sorts a range using the Sheets API SortSpec objects. It implies sorting functionality and distinguishes from sibling tools like sort_by which may have different behavior. However, it lacks specificity about the scope or variations.

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?

No guidance on when to use this tool versus alternatives (e.g., sort_by or manual sorting). No context about prerequisites or best practices.

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