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

Annotations already declare readOnly, idempotent, non-destructive behavior, so the description mainly needs to add operational context. It does that by stating the output form, the n range, the x402/Solana price, and the equivalent HTTPS endpoint; it stops short of explaining payment flow or failure behavior.

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 front-loaded with the core behavior, then adds a compact example and operational details. Every sentence contributes useful information for a paid API call, with no wasted prose.

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?

For a simple deterministic math-prefix tool with one parameter and no output schema, the description gives enough to call it correctly: what it returns, the example output, valid n range, and cost/endpoint details.

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?

The sole parameter has 0% schema description coverage, so the description must carry the meaning. It defines n as the number of initial terms and gives the 1-to-4096 range plus an example, making the parameter clear despite the missing schema description.

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 states a specific resource and output: the first n Kolakoski terms as a string of digits 1 and 2, with a concrete example. It distinguishes the prefix behavior, but it does not explicitly contrast with nearby siblings such as kolakoski, kolakoski_run, kolakoski_check, or kolakoski_sum.

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?

It gives the valid n range and an example, but it does not say when to use this tool versus alternatives like kolakoski, kolakoski_run, or kolakoski_sum. The agent must infer the selection criteria from the tool name alone.

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