search_datasets

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

No annotations are provided, so the description must fully disclose behavioral traits. It only implies a read operation, but does not explicitly state whether the tool is read-only, destructive, or requires authentication. It lacks details on side effects, rate limits, or authorization needs.

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 well-structured with a clear first-line summary, followed by an Args list with parameter names and descriptions, and a Returns section. Every sentence is informative and no unnecessary words. It is concise yet comprehensive.

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 5 parameters (1 required), no annotations, and an output schema, the description covers the tool's purpose, all parameters with examples, and the return format including hints for further use with sibling tools. It provides sufficient context for an agent to understand and invoke the tool correctly.

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 schema has 0% coverage (only titles and types), but the description provides detailed semantics for all parameters: e.g., 'Full-text search, e.g. 'crime reports'', 'Restrict to one portal, e.g. 'data.seattle.gov''. This adds significant meaning beyond the schema, helping the agent understand how to use each parameter.

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 'Search open-data catalogs for datasets (Socrata Discovery API)', specifying the verb 'search', resource 'datasets', and the API used. It distinguishes the tool from siblings like export_csv, get_dataset, etc., which have different purposes.

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 explains when to use the tool (to search datasets) and provides guidance: 'Use each result's domain + id with the other tools.' It does not explicitly exclude alternative uses, but the context is clear.

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