format_numbers

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

Discloses allowed kind values and range format, but no annotations are present, so description carries full burden. Lacks details on side effects, error handling, permissions, or revertibility.

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?

Two concise sentences: first states purpose, second explains parameters. No unnecessary words, effectively front-loaded. Minor improvement could be listing values more structured.

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 3 required parameters, no output schema, and no annotations, the description is sparse. Lacks information on return values, error cases, or comparative guidance among many sibling formatting tools. Needs more context for effective selection.

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 description coverage is 0%, but description adds meaning for 'kind' (lists allowed values) and 'range' (A1 or natural refs). However, 'spreadsheet' parameter is not explained, leaving ambiguity about its format (ID vs URL).

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?

States 'Apply a number format to a range', which is a clear verb-resource pair. Differentiates from siblings by focusing on number formats, but does not explicitly distinguish from similar tools like format_cells.

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 no guidance on when to use this tool versus alternatives like format_cells or other formatting tools. No context on prerequisites or appropriateness.

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