Search Hermes Atlas projects

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

With no annotations, the description carries the full burden. It discloses the scope (100+ community-built items), that queries can be natural language, and lists all category filter options. It does not describe the return format or ordering, but it provides substantial behavioral context that goes beyond the schema, such as what the category values are and the default limit.

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 concise but complete, front-loading the purpose then providing examples and parameter details. The category list is long but necessary, and every sentence adds value. It is well-structured and not verbose.

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?

The description covers the essential context: what the catalog contains, how queries work, and all filter options. It lacks mention of the return structure (what a result looks like) but given this is a search tool and there is no output schema, it is reasonably complete. It could improve by noting that results are matching projects, but it is sufficient for a qualified agent.

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%, so the description fully compensates by explaining every parameter: query is described with natural language and examples, category is given an explicit enum list, and limit is defined with a range (1-50) and default 10. This adds meaning well beyond the bare schema fields.

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's function: searching the Hermes Atlas catalog of 100+ community-built tools, skills, plugins, etc. It uses a specific verb ('Search') and identifies the resource ('Hermes Atlas catalog'), distinguishing it from siblings like get_project or list_by_category by emphasizing natural language querying across multiple project types.

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 provides clear context: it explains natural language queries, optional category filters, and a limit. It implies use for broad catalog searches but does not explicitly contrast with sibling tools like list_by_category or get_guide. It offers examples of queries and enumerates filter values, but no exclusionary guidance.

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