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

Annotations cover the safety profile (readOnlyHint=true, openWorldHint=false), and the description layers on substantive behavior: citations are validated against the retrieved corpus, ungrounded ones are flagged in 'citations.ungrounded' with 'citations_grounded=false'. It also draws an honest boundary ('this guards the citations only — never read it as a verdict on whether your finding itself is real'), which is exactly the kind of caveat an agent needs.

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 main purpose and the four numbered deliverables are front-loaded, and the guard explanation is a useful, non-redundant sentence. It is on the verbose side with nested parentheticals, but every clause carries information rather than filler.

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 no output schema and a read-only analysis tool, the description carries the full burden and meets it: it describes the four brief sections and the citations_grounded structure of the return. Combined with the explicit sibling contrast, an agent has everything needed 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 description coverage is 0%, so the description must compensate. It explains the 'query' parameter well (optional override of retrieval text, defaulting to the finding itself) and clarifies 'finding' via the paste instruction, but the 'limit' parameter (default 15) is left entirely unexplained. Two of three params are meaningfully covered, so a mid score.

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+resource: a 'submission & escalation co-pilot' that turns a draft finding into a grounded brief. It even enumerates the four deliverables, so the agent knows exactly what it returns. It explicitly distinguishes itself from the sibling find_attack_approaches ('which returns the raw prior-art cards').

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?

Tells the agent to paste a DRAFT finding plus what was tried/couldn't be achieved, which gives clear situational context. It names and contrasts the closest sibling, routing the agent appropriately. It stops short of an explicit when-not condition, so 4 rather than 5.

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