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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds real behavioral context beyond that: paginated long guides and the nextOffset continuation signal, which an agent would not otherwise know. Missing: what a doc entry looks like and whether topic names are case-sensitive.

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?

Three short sentences, zero filler, with the core purpose front-loaded and the discovery and pagination hints following in priority order.

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?

No output schema exists, yet the description still discloses the listing mode and the pagination contract, which is the minimum an agent needs to drive a two-param reader. A brief note on valid topic identifiers would close the remaining gap.

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 0%, so the description must carry the burden. It explains both params at a functional level (omit topic to list; offset pages through long guides), but leaves the format of `topic` undefined and never reconciles the `offset` parameter name with the returned `nextOffset` value, which invites a mis-call.

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?

States a specific verb and resource: reads KerfScript language and JavaScript integration documentation for building laser-cutting generators. Clear what the tool returns (docs) versus the sibling names kerfscript_examples/parameters/render, though it never explicitly contrasts itself with kerfscript_examples, which is the closest overlap.

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?

"Omit topic to list guides" gives a concrete entry pattern and is genuinely useful for discovery. But there is no guidance on when to prefer this over kerfscript_examples or kerfscript_parameters, and no statement of preconditions or typical call flow.

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