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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds real behavioral value beyond that: it discloses what results contain (access requirements, source links, limitations) and that research items are 'separately labelled', which tells the agent how to interpret the payload. No permissions or rate-limit context, but none is implied by the annotations.

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 tight sentences with no filler. The usage trigger, filtering capability, result contents, and exclusions are all packed in and the operative conditions lead the text.

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?

An output schema exists, so return values need not be re-specified, and the description still usefully summarizes result composition. The main gap is the missing routing relationship to the sibling get_capability, which an agent would need to choose between the two confidently.

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%, so the description carries the burden. It maps meaningful filters ('type, category, or protocol') onto kind, category, and protocol, but leaves limit and the semantics of query itself undocumented. Partial compensation, not full, so a 3 is warranted.

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 first sentence names a specific verb (search) and resource (documented tool, hosted agent, or framework), and the title reinforces it. However, it never contrasts with its sibling get_capability, so the agent must infer the search-vs-fetch split from the name alone.

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 gives a clear trigger ('when a task needs a documented tool, hosted agent, or framework') and two explicit exclusions (retrieving private handoffs, executing a provider). It stops short of naming the sibling get_capability as the alternative for fetching a single known capability.

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