list_helixir_tools

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

With no annotations, the description carries the full burden. It discloses that the tool returns a catalog with summaries, triggers, input shape, and tags. It does not explicitly state read-only or non-destructive behavior, but the context implies it is a listing/discovery operation. No contradictions.

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?

Two sentences plus a parenthetical note. Extremely concise, front-loaded with the primary purpose. Every sentence adds value without redundancy.

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?

Despite no output schema, the description thoroughly explains what the response contains (every tool with summary, triggers, input shape, tags). Given the tool's purpose as a catalog, this is fully sufficient.

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% and the description adds value by explaining parameter semantics: 'Restrict to tools matching ALL supplied tags' and 'Substring match on tool name' – clarifying the matching logic (AND vs OR) and what 'search' operates on.

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 it is a discovery tool for the helixir MCP tool catalog, listing all registered tools with summaries, triggers, input shapes, and tags, with filtering by tag or substring. This directly distinguishes it from sibling tools that are specific actions.

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?

Explicitly advises 'Use this FIRST when you are unsure which helixir tool fits a task,' providing clear when-to-use guidance and implied when-not-to-use (when you already know the tool). Also notes 'install ≠ adoption' for nuance.

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