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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is carried. The description adds genuinely useful context beyond that: the specific corpora searched and the shape of results (public document IDs, titles, canonical URLs), which orients the agent before invoking.

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?

A single front-loaded sentence that covers verb, scope, and return shape with no filler or repetition of the title.

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 and full parameter documentation, the description only needs to establish corpus scope, which it does. Minor gaps (ranking behavior, result-count limits) are not critical given the structured coverage.

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?

There is only one parameter with 100% schema description coverage, so the schema already defines `query` as a natural-language string. The description adds no format, length, or syntax guidance beyond the schema, making the baseline 3 appropriate.

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 gives a specific verb (searches) and names the exact resource scope (RocketVault public product facts, solution pages, docs, guides, grounded coverage), so an agent can distinguish it from compare_plans or fetch. It stops short of explicitly contrasting with the siblings, but the corpus description makes the intent unambiguous.

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 is implied by the corpus scope: an agent can infer this is for public RocketVault knowledge lookup rather than marketplace searches. There is no explicit when-to-use/when-not or a pointer to fetch/search_marketplace_listings as alternatives, so guidance remains implicit.

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