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

Annotations already declare readOnly, idempotent, non-destructive and openWorld=false, so the safety profile is covered. The description adds real value beyond that: return fields (title, excerpt, URL), ranking ('best match first'), and the no-account requirement. This is solid added context, though no mention of rate limits or result-count 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?

Three tight sentences, front-loaded with the verb and scope, then return shape, then the account requirement. No filler; every sentence carries information.

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 an output schema present, the description needn't explain return values, and annotations cover safety. It still supplies scope, content types, ranking, and auth-free access. The only minor gap is not distinguishing itself from sibling search tools.

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 67%: query and collection are documented in the schema, but limit is not. The description adds no parameter-level detail (no query syntax tips, no limit guidance), so it does not compensate for the gap and simply rests on the schema baseline.

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+resource ('Searches the public competitive intelligence library on debriefing.io') and enumerates the content types covered (guides, glossary, comparisons, alternatives, profiles, intel posts). It clearly signals a read-only search, but it never names its closest siblings (search_public_briefs, search_signals) to differentiate scope precisely, so the agent must infer the boundary.

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?

Usage context is implied by 'public competitive intelligence library' and the note that it 'Needs no Debriefing account', which usefully tells the agent no auth is required. However, there is no explicit when-to-use vs alternative guidance against search_public_briefs or search_signals.

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