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

Annotations already establish readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds genuinely useful behavior beyond the schema: default 50, hard server-side cap of 200, and newest-first ordering, which tells the agent how to interpret result size and recency.

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?

Three short sentences, zero filler, with the scoping filter and ordering stated before the limit/return details. Every sentence earns its place.

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, the description supplies the return shape ({verdicts, count, limit, jobId}) and the key size constraints, which is enough to call it correctly. It stops short of defining what a 'verdict' contains or how truncated results should be paged, but nothing critical 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%, so both parameters are already documented there. The description restates the default/cap for limit rather than adding new semantics (e.g., whether limit can exceed the cap silently or errors), 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 ('List recent capture verdicts') plus ordering ('newest first'), so the agent knows exactly what it gets. It does not name or contrast any sibling tool, so it falls short of the 5 bar, but the purpose is unambiguous.

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?

'Optionally filter by jobId' implies the filtering use case and the schema repeats that omitting it returns all jobs. There is no explicit when-to-use/when-not, no mention of pagination strategy when the 200 cap is hit, and no named alternative for narrower queries.

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