Google api read

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds one genuine behavioral fact beyond them: invocation is validated against the API's Discovery contract. It says nothing about credentials/scopes required, pagination, or how underlying errors surface, which matters for a generic proxy with an open-ended params blob.

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?

A single front-loaded sentence with no filler, and the read-only constraint plus the Discovery-validation guarantee are both stated up front. It is efficient, though arguably under-specified rather than genuinely concise for a tool this generic.

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?

An output schema exists, so return values need no explanation. But for a four-parameter dispatcher across arbitrary Google APIs, the description omits the discovery workflow, the shape of the params object, version selection, and any exclusion versus google.api.call. That leaves real gaps an agent cannot resolve from structured data.

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%, so all four parameters (api, method, params, version) are undocumented in the schema. The description only obliquely implies api and method via 'any listed Google API' and 'read-only method'; it never explains that params is a free-form pass-through of the underlying method's arguments or what version defaults to. The compensation is far from sufficient.

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 states a specific verb and resource: 'Run a read-only method of any listed Google API.' That is meaningfully more precise than the title and makes the read-only nature explicit. It does not, however, distinguish this from the sibling google.api.call, which an agent must infer is the write-capable counterpart.

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?

There is no when-to-use guidance and no mention of alternatives. An agent is not told to use google.api.methods or google.api.describe to discover valid method names first, nor told to prefer a purpose-built sibling (e.g. bigquery.query.run, ga4.report) over this generic escape hatch.

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