ecosystem_search_by_capability

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

No annotations exist, so the description must disclose behavior. It only states the search operation but does not mention authentication needs, rate limits, side effects, or return format. The presence of an output schema partially compensates, but behavioral context is minimal.

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 short sentence that front-loads the core purpose. It is efficient but could benefit from minimal additional structure. No waste.

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 7 parameters and many sibling tools, the description is incomplete. It does not explain result ordering, tag semantics, or how to combine parameters effectively. The output schema exists but the description should provide higher-level context.

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 43% (3 of 7 parameters documented in schema). The description does not explain any parameters. For a tool with 7 parameters, especially with low coverage, description should add meaning but does not. Baseline with no param info and low coverage is 2.

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', the resource 'ecosystem repos', and the method 'by capability tags' with the clarification 'reverse lookup from tag → repo'. It distinguishes from siblings like ecosystem_search (general search) and ecosystem_repo_tags (get tags for repo).

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 guidance is provided on when to use this tool versus alternatives. With numerous sibling tools (ecosystem_search, ecosystem_repo_get, etc.), the description fails to offer decision criteria or exclusions.

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