datacloud_query_rows

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

No annotations are provided, so the description must cover behavioral traits. It mentions pagination via offset and row_limit, but fails to disclose important details such as error handling for incomplete queries, response format, or ordering guarantees. The description is adequate but lacks depth.

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 concise sentence with no fluff. However, it could be slightly more informative without losing conciseness. Structure is fine for a short description.

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 complexity of the tool (requires a submitted query, pagination, output schema present), the description is too sparse. It does not mention the dependency on datacloud_submit_query or datacloud_query_status, nor explain what happens if the query is still running. The description lacks contextual completeness.

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%, but the description does not add any meaning beyond parameter names. It does not explain query_id's required role, offset/row_limit behavior (e.g., max limits, starting index), or defaults. The parameter semantics are weak.

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 returns paginated rows for a submitted Data Cloud SQL query. It uses a specific verb 'Return' and resource 'paginated rows', and distinguishes itself from sibling tools like datacloud_submit_query, datacloud_query_status, and datacloud_cancel_query.

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 implies usage after a query is submitted via datacloud_submit_query, but does not explicitly state when to use it vs alternatives, nor provide warnings about prerequisites (e.g., query must be completed) or exclusions.

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