Compare 2-5 read-only HeyClaude entries by fit, category, platforms, source metadata, and install complexity.
| Name | Required | Description | Default |
|---|---|---|---|
| entries | Yes | 2–5 entries to compare, each identified by category and slug. | |
| platform | No | Target platform for the comparison (affects install steps shown). |
| Name | Required | Description | Default |
|---|---|---|---|
| ok | Yes | ||
| policy | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false. Description confirms 'read-only' but adds no additional behavioral traits beyond what annotations provide.
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?
Single sentence is front-loaded with key info: verb, resource, constraints, and comparison dimensions. No wasted words.
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 presence of an output schema and read-only nature, the description sufficiently covers purpose, scope, and comparison dimensions. Missing guidance on error conditions but 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 coverage is 100%, but description adds value by listing comparison aspects (fit, category, platforms, etc.) not present in the schema. It also clarifies the 2-5 range already in schema.
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?
Description uses specific verb 'compare' and resource 'HeyClaude entries', with clear scope '2-5' and comparison dimensions. It distinguishes from sibling tools like entry.detail which focus on single entries.
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?
Description implies usage for comparing entries by various criteria but does not explicitly state when to use or avoid this tool versus alternatives like entry.detail or registry.search.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools have distinct purposes, especially with clear prefixes. However, there is some overlap between entry.safety and entry.trust (both deal with safety/trust metadata), and between registry.recommend and registry.plan (both provide recommendations). The descriptions help differentiate but some ambiguity remains.
All tool names follow a consistent pattern: a domain prefix (entry, install, registry, submission) followed by a descriptive noun, all lowercase with underscores. This makes the surface predictable and easy to navigate.
27 tools is slightly high but reasonable given the broad scope of the HeyClaude registry, which includes browsing, recommending, installing guidance, and submission preparation. The count is appropriate for the server's purpose.
The tool surface is comprehensive, covering search, detail, comparison, safety/trust analysis, install setup for multiple clients, recommendation, and a full submission pipeline (validation, review, schema, etc.). There are no obvious gaps for the intended read-only registry directory functionality.
