sort_worksheet

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

The description explains the sorting behavior and parameters, but without annotations (which are absent) it falls short on disclosing important traits like whether the sort is in-place, destructive, or reversible. 'Returns Success message' 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?

Extremely concise: a one-line summary followed by a bulleted Args list and Returns line. No unnecessary words; every sentence serves a purpose.

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 context of many sibling worksheet tools, the description should clarify if sorting is in-place or returns a new view. It does not mention stability or handling of headers. The output schema is a simple success message, so return value detail is adequate.

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?

With 0% schema description coverage, the description compensates by defining each parameter: 'col: Column to sort by (1-based)' and 'descending: Sort high-to-low when True'. This adds meaning beyond the raw schema types.

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 'Sort all rows of a worksheet by one column,' which is a specific verb and resource. It distinguishes itself from sibling tools like add_columns or set_worksheet_data by focusing on sorting.

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., manual sorting, other sorting tools). Lacks context on prerequisites, such as whether the worksheet must have data or if only one column can be sorted at a time.

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