sort_range

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

Discloses important behaviors: sorting order (numbers/dates before text, blanks last), that formatting stays put, formulas move as text without adjusting relative references, and stability for multi-key sorts. No annotations provided, so description fully covers transparency.

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?

Front-loaded with main action, then concise bullet-like details. Each sentence adds value, though slightly long for a description.

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 no output schema and 5 parameters, the description covers key behaviors and parameter usage. Explains important side effects (formatting, formulas). Lacks mention of return value, but sorting typically modifies sheet in place.

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?

Adds meaning to by_column (sheet column letter) and has_header (keep header). Does not explain range format or descending, but schema coverage was 0% so description compensates well. Could be slightly more explicit on range format.

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 sorts rows by one column's values, specifying verb, resource, and method. It distinguishes itself from sibling tools like remove_duplicates or apply_auto_filter.

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?

Provides explicit guidance on using by_column as a column letter, has_header to keep header, and multi-key sort procedure. Does not explicitly state when not to use, but sufficient for correct invocation.

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