Raw Google Sheets API call

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

Beyond the annotations (destructive, open-world, not idempotent), the description discloses that the Bearer token is added automatically, that the method defaults to GET with PUT for values updates, that the path may carry a query string, and that batchUpdate requests are atomic. These details materially affect how an agent invokes the tool and what it should expect.

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 dense and front-loaded with purpose, but the list of examples is long. Each example earns its place by illustrating what the typed tools do not cover, yet the sentence could be slightly more compact. Overall, it is well-structured and every sentence contributes value.

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?

For a generic raw API tool with no output schema, the description covers the key operational aspects: path construction, method selection, body usage, authentication, and scope restriction. It also includes representative use cases that signal to the agent what kinds of operations are possible. Nothing essential is missing for an agent to invoke this correctly.

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 schema already provides 100% coverage for the three parameters, so the baseline is 3. The description adds useful semantic context beyond the schema: an example path format, the body shape for batchUpdate, the note that methods are limited to GET/POST/PUT, and the reminder that body is for POST/PUT only. This is meaningful but not exhaustive, so a 4 is appropriate.

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 identifies the tool as an escape hatch for arbitrary Google Sheets API v4 paths, with a specific verb ('call any ... path directly') and a clear resource boundary ('Sheets API paths only'). It distinguishes itself from the typed sibling tools by stating it covers requests they don't. The examples further clarify the intended scope.

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?

The description explicitly states when to use this tool: 'for requests the typed tools don't cover', and provides concrete examples like batchUpdate with mergeCells, slicers, and developer metadata. It also gives an exclusion ('Drive paths are not reachable here') and explains the default method behavior, giving an agent enough to decide between this and a typed sibling.

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