heliusKnowledge

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

With no annotations provided, the description takes on full burden. It correctly indicates the tool is non-mutating ('not live mutations'), which implies read-only behavior. However, it lacks details on side effects, error handling, or return behavior, so it is not fully transparent.

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 sentence followed by a short usage note, both front-loaded and concise. Every part adds value with no 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?

Given the complexity (21 parameters, 17 action enums, no output schema, no annotations), the description is too brief. It does not explain the purpose of each action or how parameters interact, leaving a significant gap in completeness.

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 only 14%, yet the description provides no guidance on the meaning of the 21 parameters (e.g., args, path, repo, slug, query, topic). It does not compensate for the low schema coverage.

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 covers 'Docs, guides, pricing references, troubleshooting, source, blog, and SIMD research.' and explicitly distinguishes from live mutations, making it clear this is a knowledge/reference tool distinct from sibling tools like heliusWrite or heliusTransaction.

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 explicitly says 'Use for guides, rate limits, or errors, not live mutations,' providing direct guidance on when to use this tool and when to use alternatives (other heliusX tools for mutations).

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