Search a Dataville data source

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

No annotations are provided, so the description carries the full burden. It clearly states the tool is a query operation, implying no destructive behavior. It does not detail potential behaviors like pagination, rate limits, or result limits, which would elevate transparency. With no annotations, this is adequate but minimal.

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 that efficiently delivers the core purpose, references the sibling tool for additional context, and mentions both the keyword and optional params. No wasted words.

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 tool has 3 parameters (100% schema coverage), no output schema, and no annotations, the description is reasonably complete for a simple query tool. It tells the agent what to query and where to find valid sources. However, it lacks information about what the output looks like (e.g., result format) which would be needed for full 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 100%, so the schema already documents all parameters. The description adds minimal value beyond the schema, only hinting that 'keywords' is a search string and 'params' are optional. It does not explain how params are used or provide examples. Baseline 3 is appropriate.

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 verb ('Query'), resource ('one of Dataville's data sources'), and key components (keyword string, optional query params). It distinguishes itself from the sibling tool by referencing list_dataville_sources for valid source names.

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 says to use list_dataville_sources to find valid source names, providing clear context for when to use this tool. However, it does not exclude any scenarios or mention when not to use it, missing a point for a perfect score.

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