search_knowledge

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint. The description adds value by specifying the OAuth scope requirement and the 'scope-gated' nature, which are behavioral traits beyond what annotations provide. No contradictions.

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 extremely concise with three sentences: purpose, OAuth requirement, and parameter details. The purpose is front-loaded, and every sentence is necessary and valuable with no extraneous 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 search tool with two parameters and an existing output schema, the description covers purpose, authentication, and parameter constraints. It lacks explanation of result ranking or 'top chunks', but given annotations and output schema, it is mostly complete.

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?

The input schema has 0% description coverage, so the description fully compensates by providing clear explanations for both parameters: 'query' (2-300 chars) and 'limit' (1-20, default 5). This adds significant meaning beyond the raw schema.

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 the tool searches a knowledge base, with the verb 'search' and resource 'extended knowledge base'. It indicates read-only and scope-gated, but does not explicitly differentiate from sibling 'search_articles', so purpose is clear but not fully distinguished.

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 mentions the required OAuth scope and sign-in requirement, providing context for when the tool is usable. However, it does not give guidance on when to use this versus alternatives like 'search_articles', nor does it explicitly state when not to use it.

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