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

The description adds substantial context the annotations do not carry: it consumes one update from the weekly research allowance, requires admin rights, and explains the retry/side-effect budget ('starts no second job and uses no allowance or daily cap a second time'). The only weakness is that this retry-dedup story sits in mild tension with the declared idempotentHint=false, leaving a small ambiguity about how retries are actually treated.

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?

Front-loaded with the core action and timing, then cost, auth, and idempotency facts. The final sentence ('starts no second job and uses no allowance or daily cap a second time') partially repeats the prior retry sentence, a mild redundancy that keeps it from a 5.

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 annotations covering the safety profile, an output schema present, and 100% parameter coverage, the description still supplies the non-obvious facts an agent needs: cost in allowance, admin restriction, and retry behavior. Nothing material to correct invocation is missing.

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 100% and the single idempotency_key parameter is fully documented in the schema itself (max/min length, purpose). The description restates the key's retry semantics but adds no syntax or format detail beyond it, so the baseline 3 applies.

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 and resource ('Refreshes the research on the core watchlist') plus the timing nuance ('now, instead of at the next cycle'). An agent can tell this is an on-demand refresh versus the scheduled cycle. It does not explicitly separate itself from siblings like research_competitor or set_monitoring_cadence, so it stops short of 5.

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?

'now, instead of at the next cycle' gives a clear condition for choosing this over waiting on the scheduled refresh, and 'Admin only' flags a prerequisite. No explicit exclusions against sibling tools are stated, so it is clear context but not full when/when-not guidance.

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