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

Annotations already declare read-only, idempotent, closed-world behavior, so the description adds valuable context beyond them: results are bounded public excerpts, not source files or bulk exports, and conflicting claims are referred to Baldwin. This helps an agent understand output limits and escalation behavior.

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 dense and front-loaded, moving from scope to return format to usage constraints. Every sentence carries relevant information, though the topic list is somewhat compressed.

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 no output schema, the description adequately explains that results are source-linked, bounded public excerpts rather than raw files. It also covers narrowing behavior and conflict handling, leaving only minor gaps around pagination and the limit parameter.

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 only 33%, but the description clarifies the 'document' parameter as a returned public reference ID rather than a server filename, and implies focused queries. It does not explain the 'limit' parameter or maximum result bounds beyond the schema's default and cap.

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 names a specific verb and resource ('Search deep Baldwin product knowledge') and enumerates the covered topics. It distinguishes itself from quote-oriented siblings by directing price questions elsewhere, though it does not explicitly differentiate itself from search_pergola_faq or get_pergola_guidance.

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?

It gives clear when-to-use guidance ('Search a focused product question'), explains how to narrow with a returned reference ID, and routes current-price requests to quote tools. It lacks explicit when-not-to-use conditions beyond the price exclusion.

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