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

Annotations already cover readOnly, idempotent, non-destructive, and non-open-world behavior. The description adds useful behavioral context: results are ranked, returns excerpts, and includes canonical source URLs. It does not mention sorting, pagination, or result count behavior, but the annotations relieve much of the burden.

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?

Two sentences with no filler: the primary action and return shape are stated first, followed by one necessary boundary condition. Every sentence earns its place.

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?

Given strong annotations and a simple two-parameter schema, the description captures scope, return type, and source of results without an output schema. It is mostly complete, though a short note on limit or result count would remove residual ambiguity.

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 0% and the description does not explain either parameter. 'query' is loosely implied by the verb 'search,' but 'limit' is never addressed. With such low coverage, the description needed to compensate but does not.

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 uses a specific verb ('Search') and resource ('the complete published corpus') and states the return type ('ranked excerpts with canonical source URLs'). The open-web exclusion is clear, although it does not distinguish any specific sibling tool by name.

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 implies when to use it: when an agent needs results from the published Bloody Hopes corpus rather than the open web. However, it does not name any alternative or provide explicit when-to-use/when-not-to-use guidance beyond the single negative statement.

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