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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false), so the trailing 'Read-only' adds nothing. The description does add genuinely useful behavior beyond the annotations: the answer is returned word for word, and on no match a fixed message with a contact email is returned — this pre-empts an agent misreading the fallback string as a real answer.

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, no filler, and the core behavior plus the fallback case are front-loaded. Every sentence carries information an agent needs to interpret the response correctly.

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 single-parameter, no-output-schema tool whose annotations already declare safety, the description covers the main behavior and the miss case, which is what an agent needs. The one remaining gap is how 'approved answer' matching is decided (exact topic vs. fuzzy), which would matter for phrasing the question.

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 description coverage is 100% for the single 'question' parameter, so the schema already carries the semantics and baseline 3 applies. The description's phrase 'by topic' adds a hint about how matching works (topic lookup rather than free-form Q&A), but it never clarifies the relationship between 'topic' and the 'question' 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?

States a specific verb and resource — looks up an approved answer by topic and returns it verbatim — which an agent can distinguish from write tools like build_cart. It does not, however, differentiate itself from overlapping informational siblings such as about_nwb, how_to_use, or get_policies.

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?

There is no statement of when to use this tool versus the informational siblings (about_nwb, get_policies, how_to_use), nor any prerequisite or exclusion. The only implicit guidance is the fallback behavior, which tells the agent what happens on a miss rather than when to reach for this tool at all.

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