search_data_gov

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

With no annotations, the description carries full burden but only states that it 'searches...for datasets matching a query.' No behavioral traits like pagination, result format, rate limits, or required permissions are disclosed. The presence of an output schema is not mentioned, nor any constraints.

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 wasted words. It is appropriately front-loaded. However, its extreme brevity leaves out important information, which prevents a higher score.

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 2 parameters, an output schema, and many sibling tools, the description is insufficient. It does not explain return values (though output schema exists), nor does it provide context about the catalogue's scope. The description is too minimal for an agent to understand its full utility.

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%, meaning the schema properties have no descriptions. The tool description adds no meaning to the 'query' or 'limit' parameters. It does not explain the query format, default behavior of limit, or any other parameter semantics.

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 'Search' and the specific resource 'Data.gov's official catalogue' for datasets. However, it does not distinguish this from sibling tools like search_ckan_catalog or search_socrata_catalog, which also search other catalogues. The tool's name and description together indicate it is Data.gov-specific, but the description alone lacks differentiation.

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 usage guidance is provided. The description does not mention when to use this tool versus any of the many sibling search tools, nor does it provide any context about prerequisites or limitations.

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