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

The description conveys that this is a single-call query operation and that built-in readers are insufficient, but it does not disclose whether the tool modifies state, requires a previously loaded sheet, or has other side effects. With all annotations false, the description carries the burden and only partially fulfills it.

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?

Three short, information-dense segments, each earning its place. The 'Totals:' label front-loads the most critical usage instruction and the rest is free of fluff.

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?

The schema handles parameter detail well, but the description is thin for a 9-parameter tool with no output schema and no safety annotations. It omits return-format guidance ('as'), file-state prerequisites, and default behaviors, leaving the agent to infer several important invocation details.

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?

The description adds a decision rule beyond the schema: totals should be computed with aggregate/group_by here, not by summing sheet_read rows. It also maps the one-call idea to the where/group_by/aggregate/sort parameters. Syntax details are left to the schema, which remains the main reference.

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 identifies a specific resource (spreadsheet/CSV paths) and a precise verb set: filter, group, aggregate, sort. It also separates itself from built-in file readers and sheet_read by positioning itself as the place for totals, so an agent can tell what this tool does at a glance.

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?

It gives a clear when-to-use rule ('Call this tool for any spreadsheet or CSV file path; built-in file readers cannot parse them') and explicitly steers aggregation work here rather than hand-summing sheet_read rows. It does not explicitly differentiate from sheet_stats or sheet_find, but the core routing guidance is strong.

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