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

Annotations already declare this as a safe, read-only, non-open-world tool, so the description does not need to restate safety. It adds content coverage about what the topics contain, but it does not describe the return format, behavior for unknown topics, or default behavior when no topic is supplied.

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 purpose is front-loaded in the first sentence, and the topic list is relevant. However, the second sentence is a long run-on with internal references like `cb` and an extensive embedded list, making it denser and less scannable than ideal.

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 one-parameter, read-only documentation tool this is mostly adequate, but with no output schema the description should more explicitly state that it returns documentation text. It also leaves unclear what happens if `topic` is omitted or unknown.

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?

With 0% schema description coverage, the description substantially compensates by explaining that `cardboard` is the editor agent's editing guide and that other topics cover commands or techniques, with many examples. It does not fully enumerate valid topic strings or clarify the optional/default behavior, but it gives the agent meaningful guidance for the sole parameter.

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 that this tool retrieves Cardboard documentation by topic, and it characterizes the `cardboard` topic versus other command/technique topics. It is distinguishable from the operational sibling tools, though it does not use an explicit verb like 'retrieve' or 'read'.

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?

Usage is implied by 'documentation by topic' and the listed topic categories, but there is no explicit instruction such as 'use this when you need documentation' or 'do not use this to perform edits.' The agent must infer when this tool is preferable to the many sibling action tools.

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