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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, but the description adds genuinely non-derivable behavior: the check is 'bounded' and 'fresh' (not cached), inputs stay constant across polls, the agent owns the polling cadence, and the operation is stateless enough that it 'may stop at any time'. That clarifies this is a one-shot pull rather than a persistent background subscription — useful context beyond the annotation set. It stops short of saying what happens if the 'bounded' check cannot complete or how polling limits are enforced.

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 short sentences, no filler, with the core action front-loaded and the read-only/polling caveat second. Every clause carries information and nothing is redundant.

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 described, and the safety/polling model is covered. But for a tool with 4 parameters at 0% schema coverage and five confusable siblings, the definition omits parameter meaning and any differentiation from the rest of the monitor family, leaving the agent under-equipped 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% for four parameters, so the description carries the full explanatory burden and largely fails it. 'One exact contract' loosely implies chain+address, but the optional includeSecurity and includeForensics flags — which materially change the payload — are never mentioned, and the chain enum with nine chains is not acknowledged either.

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 identifies an action (a 'bounded fresh check') and a resource ('one exact contract'), which is more than a tautology. However, against siblings named create_asset_monitor, check_asset_monitor, list_asset_monitors and stop_asset_monitor, it never clarifies whether this creates a monitor, checks one, or performs a standalone one-shot check — 'same inputs on each poll' implies repeated invocation but the tool takes no monitor ID, leaving the relationship to the monitor family ambiguous.

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 explicit when-to-use guidance and no alternatives are named despite five sibling tools in the same monitor family. The sentence about polling frequency describes the operating model rather than routing the agent to the correct tool, so an agent has no stated basis for choosing this over check_asset_monitor or create_asset_monitor.

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