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

Annotations already declare readOnly/idempotent/openWorld/non-destructive, but the description adds that it is 'Public documentation; needs no scope and touches no workspace data', which clarifies auth requirements not in annotations, and explains the excerpt nature of results. It stops short of describing result count or rate limits.

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?

Front-loaded with the core action and the routing instruction, then gives the trigger list and the excerpt caveat. The parenthetical example list (Google Workspace, Microsoft 365, Zoho Mail, Front, …) is slightly heavy but genuinely narrows the trigger scope.

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?

An output schema exists so return values needn't be spelled out, yet the description still notes results carry 'titles and links'. Combined with the scope statement and the handoff to read_docs_page, an agent has everything needed to call this correctly.

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%, so query, context, and language are already fully documented in the schema. The description only marginally links results to the sibling's input ('pass the page path from a result to read_docs_page'), which is not a parameter of this tool, so baseline 3 applies.

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 ('Search the official Scribe help-center documentation') plus the exact domain, and clearly distinguishes itself from the sibling read_docs_page by characterizing output as excerpts versus a full guide.

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?

Explicitly says 'ALWAYS use this before answering product/how-to questions from memory' and 'before telling a user something isn't possible', enumerating trigger topics and naming the alternative (read_docs_page) with the condition that selects it.

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