query_datacloud

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

No annotations are present, so the description must supply all behavioral context. It does not disclose whether the query is read-only or destructive, how authentication works, or what the response format is. The presence of an output schema is not leveraged.

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 sentence with no wasted words, but it is too minimal. It front-loads the purpose but omits critical details, making it less helpful than a more structured description with usage notes.

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 the presence of multiple sibling Data Cloud tools and a single parameter with no schema description, the description is inadequate. It does not explain the output, error behavior, or how this tool fits into the query lifecycle.

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 single parameter sql_or_query has 0% schema description coverage. The description does not clarify what this parameter expects (e.g., SQL text, a query ID) or provide any format constraints, leaving the agent to guess.

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 action (run a query) and resource (Data Cloud), but it does not differentiate from sibling tools like datacloud_submit_query or datacloud_query_rows, leaving ambiguity about what specific query operation this tool performs.

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 such as datacloud_submit_query or datacloud_query_rows. There are no examples, prerequisites, or exclusions given.

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