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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds useful behavioral context: it is a public library search requiring no account, and results are ordered best match first.

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 tightly written sentences with no filler. The purpose, return shape, and account requirement are front-loaded and each sentence contributes useful 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?

For a public search tool with an output schema and rich annotations, the description covers what is searched, what is returned, ordering, and the no-account requirement. It omits any explanation of the limit parameter's default behavior, but otherwise an agent has enough to call it 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 coverage is 67%; query and collection have schema descriptions, and the description's list of content types loosely maps to the collection enum. The limit parameter remains undocumented in both schema and description, and no additional syntax or default behavior is supplied.

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: 'Searches the public competitive intelligence library on debriefing.io' and enumerates the content types covered. It does not explicitly differentiate itself from related sibling tools such as search_public_briefs or search_signals, so it falls short of the sibling-distinguishing clarity required for a 5.

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 implies use for public-library searches and notes 'Needs no Debriefing account,' which is helpful context. However, it gives no explicit when-to-use guidance against alternatives like search_public_briefs or search_signals, leaving selection largely to inference.

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