sheets_add_named_range

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

The description discloses no behavioral traits beyond the action itself. With no annotations provided, the description fails to mention side effects (e.g., overwriting existing named ranges), permission requirements, error behavior, or any constraints on usage.

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 short sentence, which is brief, but it is under-specified for a tool with 7 required parameters. It lacks necessary detail about how to specify the range, making it inadequate rather than appropriately concise.

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?

With 7 required parameters, no annotations, and no parameter descriptions, the tool is complex enough that a one-sentence description is grossly incomplete. It fails to explain the coordinate system, whether named ranges can be overwritten, or what the output format is, despite the existence of an output schema.

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%, and the description does not compensate by explaining what any of the 7 parameters (e.g., sheet_id, start_row, end_col) mean. It only mentions the high-level resource, leaving parameter semantics entirely unclear.

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's function: 'Create a named range in a spreadsheet.' It uses a specific verb ('Create') and resource ('named range'), and it distinguishes from sibling tools like sheets_add_sheet and sheets_add_chart by explicitly mentioning 'named range'.

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 is provided on when to use this tool versus alternatives. There is no mention of use cases, exclusions, or alternative tools, leaving the agent to infer appropriate usage from the name alone.

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