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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. Beyond that the description adds useful behavior: pattern filters content and results are paginated, plus it enumerates returned fields (URL, event count, reason, time). It stops short of noting rate limits or auth, but that is acceptable given the annotation coverage.

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?

A single semicolon-delimited sentence that is front-loaded with the purpose and then the filter/pagination behavior. Dense but every clause carries information; no 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 an output schema present, the field enumeration is somewhat redundant, but the description still supplies the filtering and pagination context an agent needs to call it correctly. Only the pattern syntax and page/limit conventions remain uncovered.

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 load: it explains that 'pattern filters the content' and that results are 'paginated', which gives meaning to pattern, page and limit. However, page/limit semantics (default 20, page indexing) and the pattern syntax (substring vs regex) are left unstated.

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: lists scans where the page wrote suspicious content to the clipboard, with a clarifying example (PowerShell commands). This is clear and distinct from generic tools, but it never names or contrasts against the obvious siblings get_clipboard_events, get_pastejacking, or get_clipboard_stats, so an agent must infer the boundary itself.

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 'for example PowerShell commands' clause implies the detection scenario and thus when this tool is relevant, but there is no explicit when-to-use/when-not and no alternative tool is named. Usage is inferable rather than stated.

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