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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the closing 'No workspace access, external fetches or writes' largely restates structured data. It does usefully confirm the guide is a static bundled artifact with no network or workspace dependency, which is modest added value over the annotations.

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?

A single front-loaded sentence whose only elaboration is a tight four-item topic map. No filler, no restatement of the title, and the safety note is kept to a short trailing clause.

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?

With one enum parameter fully documented and an output schema present, the description need not explain return values. Purpose, topic selection, and the safety profile are all covered, leaving nothing an agent needs in order to select and invoke it.

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 enum already lists the four topic values, but the description adds meaning the schema does not: what content each topic contains (grammar/limits/examples, tags/duplicates/formatting, batches/recovery, review/rating), giving the agent a basis for choosing a topic.

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 verb and resource ('Returns a bundled Nibomo reference guide') and enumerates the four topic domains with a parenthetical of what each covers, so an agent can tell it apart from sql_execute/sql_query siblings without opening the schema.

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 topic parentheticals imply when each guide is relevant, but the description never states when to call this tool versus siblings like sql_execute or next_review_card (e.g. 'consult before writing SQL'). Usage is inferable rather than explicit.

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