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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds 'Keyless' (no authentication required) and details about the catalog contents, which provides some extra context beyond annotations but does not deeply describe behavior like rate limits or return structure.

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 begins with the action verb 'Search' and the target resource, followed by essential details. It is concise, front-loaded, and contains no redundant or irrelevant information.

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?

For a search tool with 3 well-documented parameters and comprehensive annotations, the description provides adequate context: the domain (USGS ScienceBase), contents, and a key usage note (Keyless). While return format is not described (no output schema), the tool’s simplicity makes this acceptable.

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%, with each parameter clearly defined (query as free-text, limit with defaults, category options). The description does not add new information about parameters beyond what the schema provides, so it meets the baseline for high coverage.

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 specifies that the tool searches the USGS ScienceBase catalog, listing the types of scientific data included (datasets, publications, projects) and key features (summaries, categories, dates, download links). It uniquely identifies the resource and differentiates from sibling tools that search other domains or provide different functionality.

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 searching USGS data and notes no API key is needed, but lacks explicit guidance on when to use this tool versus alternatives like deep_research or search_within. There are no exclusion criteria or recommended scenarios.

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