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

With no annotations provided, the description carries the full behavioral disclosure burden. It discloses that the tool monitors recent activity for specific categories, which is useful, but it does not explicitly state that it is read-only, what the returned alert format looks like, how 'suspicious' is determined, or whether it queries on-chain or relies on off-chain indexes.

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 description is a single, information-dense sentence that front-loads the verb and resource, then lists the specific event types monitored. Every word adds value and there is no redundant or filler content.

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?

For a simple 3-parameter read-oriented tool, the description and schema cover invocation adequately. However, since there is no output schema, the description should have provided some indication of what the tool returns (e.g., a list of flagged events or risk summaries), and it does not.

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%, so the schema already documents chain, address, and lookbackHours clearly. The description adds no extra parameter semantics beyond aligning 'recent' with lookbackHours, so the baseline score of 3 is 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 states a specific verb ('Monitor') and resource ('recent contract activity'), enumerating concrete signal types: suspicious admin operations, proxy upgrades, ownership changes, and pause events. It is clear and not a tautology, though it does not explicitly contrast itself with any sibling tool like approval_scan or code_review.

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?

The description implies the tool should be used when the agent needs to detect risky governance or admin activity on a contract, which provides some usage context. However, it offers no explicit when-to-use versus alternatives, no exclusion cases, and no mention of when another tool like code_review or token_intel would be more appropriate.

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