eth_search_resources

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, so no contradiction. The description adds the API and feature list (full-text, field search, facets, pagination), but does not provide deeper behavioral context like rate limits or return format. Adequate but not exceptional.

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 three short sentences that efficiently convey purpose, underlying API, and supported features. No wordiness or redundancy; each sentence adds distinct value.

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's complexity (multiple parameters, pagination) and presence of an output schema, the description covers the core purpose and features but omits details on error handling, auth, or rate limits. Adequate for a straightforward read-only search tool.

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?

Despite the context signal indicating 0% schema description coverage, the actual input schema includes detailed descriptions for all parameters (e.g., query format with field, operator, value). The description only adds a high-level summary of features, which does not significantly enhance what the schema already provides. Baseline score of 3 applies.

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 searches the ETH library catalog with over 30 million resources, mentioning the specific API and supported features. This distinguishes it from sibling tools like eth_get_resource (single resource) and eth_search_archive (archive-specific).

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 does not provide explicit guidance on when to use this tool versus alternatives. No 'use this for general search; use eth_search_archive for archives' or similar advice. Usage context is implied but not clarified.

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