Search ecosystem integrations

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

Annotations already establish read-only/idempotent behavior, and the description adds valuable context beyond them: the dataset is offline, contains 234 entries, and returns name, category, chains, and links. It does not explain matching behavior, but the key traits are well covered.

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 one dense, front-loaded sentence with no wasted words. The enumerated categories, offline flag, entry count, and return fields all earn their place and improve usability.

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 simple closed-world search tool with no output schema, the description covers the dataset's source, size, offline nature, search dimensions, and returned fields. It is only slightly incomplete in not steering users toward sibling tools and not listing the full category taxonomy.

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?

With 0% schema description coverage, the description must compensate. It tells the agent that queries can be keywords or categories and lists output fields, but it does not clarify that category is expressed through the query string rather than a separate parameter, nor does it explain the limit parameter semantics beyond the schema's defaults.

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 names a specific verb and resource: 'Find Avalanche ecosystem integrations,' and adds concrete scope with 234 entries and example categories. This clearly differentiates it from sibling search tools like avax_search_docs or on-chain data tools.

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?

Usage is implied: use this when searching ecosystem integrations by keyword or category. However, there are no explicit when-to-use or when-not-to-use statements, nor any named alternatives despite the large sibling tool list.

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