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

With no annotations, the description must carry the behavioral burden; it only says this is a search and that the collection is aggregated. It does not disclose matching behavior, source caveats, query limits, or rate-limit expectations.

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 short and front-loaded, which suits a one-parameter tool. However, the lead-in 'BreachDB Search:' adds little information and the sentence mostly restates the tool's name.

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?

Despite an output schema, the agent cannot tell what query values are valid or when to prefer this tool over siblings. At least one critical detail (q semantics) is missing, so the description is not complete enough for reliable invocation.

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 0% and the description never explains q. The name 'q' implies a query string, but what should be searched (email, username, domain, hash) is left entirely to inference.

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 verb ('search') and a resource ('aggregated breach collection'), so it is not a pure tautology. But 'aggregated breach collection' is vague and does not differentiate this tool from sibling breach-search tools like breach_aggregator or breachsearch.

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?

There is no guidance on when to use BreachDB over the many adjacent breach tools. No exclusions, alternatives, or conditions are mentioned.

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