query_dataset

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

No annotations are provided, so the description must carry the full behavioral burden. It discloses the 1000-row cap per call, which is valuable, but it does not mention pagination via offset, error behavior, or authentication requirements. The transparency is moderate but incomplete.

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, front-loaded with purpose, and includes practical examples without any waste. Every word contributes to understanding the tool's function and syntax.

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?

The description effectively covers the core query capabilities and the row cap, which are the most critical aspects. The existence of an output schema covers return values, so the description doesn't need to explain them. Minor gaps like offset/limit semantics are not explicitly addressed, but they are intuitive from parameter names.

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 0% schema description coverage, the description compensates by providing concrete examples for select, where, group, and order. Other parameters like dataset_id, domain, limit, and offset are self-evident from their names and defaults, so the overall parameter understanding is good.

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 runs a SoQL query against a dataset, which is specific and distinct from sibling tools like search_datasets, get_schema, and profile_column. The examples reinforce this unique purpose.

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 for querying data with SQL-like clauses, and the examples demonstrate syntax. It does not explicitly state when not to use it or mention alternatives, but the context is clear enough for a knowledgeable agent.

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