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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the read-only behavior is covered. The description adds a meaningful behavioral detail about the slug coming from a previous get_help search result, but otherwise does not go beyond 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?

The description is two sentences, introduces the purpose immediately, and gives the two usage modes in one compact sentence. Every part earns its place and the topic examples are useful without bloating the text.

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 read-only tool with no required parameters, an output schema, and full schema coverage, the description is complete enough. It could mention mutual exclusivity of query and slug more forcefully, but the schema already covers that and the overall context is sufficient.

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%, so parameters are already documented. The description adds semantic value by explaining the relationship between query and slug: query searches by topic, while slug opens an article directly. This is more than merely repeating schema text.

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 opens with a specific verb and resource: 'Find practical Tokenbooks instructions or accounting guidance.' It also distinguishes the two primary modes (query search vs. direct slug access), which clearly separates this help tool from the financial operation siblings listed in context.

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 gives explicit usage guidance: pass a query to search by topic, or pass a slug to open a specific article from a previous search. It does not name alternative tools or explicit exclusions, but the context is clear and the instructions are actionable.

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