Run analytics query

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

The description reinforces the read-only nature already indicated by the readOnlyHint annotation, adding details like 'no side effects' and 'classified as a read operation'. It also discloses the max query length and that it's a POST endpoint, providing useful behavioral context beyond the annotation.

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 two sentences long, front-loading the core purpose in the first sentence. The second sentence adds essential usage guidance (use catalog first). Every sentence is valuable without redundancy, making it highly concise and well-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?

For a tool with 2 parameters, 100% schema coverage, and readOnlyHint annotation, the description covers purpose, parameter details, and prerequisites. It lacks explicit mention of the result format (e.g., array of rows), but given no output schema, this is a minor gap. Overall, it is sufficiently complete for most use cases.

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?

With 100% schema coverage, the baseline is 3. The description adds meaningful context for the 'user_scoped' parameter by explaining the default behavior and admin permission requirement, which goes beyond the schema description. For 'query', it reinforces but does not significantly extend beyond the schema.

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 action (runs a read-only GoogleSQL SELECT query), the target resource (SpotDraft's analytics tables), and the output (returning result rows). It distinguishes itself from sibling tools by mentioning get_analytics_catalog as a prerequisite and specifying constraints like max query length.

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 advises to use get_analytics_catalog first to understand available tables/columns, providing clear context for when to use this tool. However, it does not explicitly state when not to use it or compare with alternatives like execute_read_request, though the read-only analytics focus is clear.

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