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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds value on top: a PREMIUM license requirement, a guarantee that invalid input never raises a protocol error but returns a structured error object, and an explicit retry-safety statement. These are operational traits an agent cannot infer from the annotations.

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 purpose, then constraints, then error behavior — a sensible order. The inline return-shape JSON is partly redundant given an output schema exists, making the description slightly longer than necessary, but no sentence is 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?

Covers purpose, exclusions, licensing, error semantics, retry safety, and input shape for a single-parameter tool with annotations and an output schema already in place. An agent has everything needed to decide and to invoke correctly, including what to do on failure.

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?

There is a single required parameter with 100% schema description coverage, so the schema already carries the semantics. The description only echoes it as an input example ('{"code": "<file contents>"}') without adding format, size, or language constraints beyond what the schema states.

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 ('Run an OWASP-oriented security pass over a source file') and immediately bounds scope with the enumerated check categories (injection, auth/session, crypto, SSRF/deserialization, path handling). It distinguishes itself from a sibling by naming complexity_report as the tool for style/structure instead.

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?

Provides an explicit positive condition ('Use on one source file when vulnerabilities are the question'), an explicit exclusion with the alternative named ('Not for style or structure (complexity_report)'), and a caveat about not replacing a human reviewer on high-risk code. The only unmentioned neighbor is secret_scan, but the vulnerability-vs-secret split is implicit in the enumerated check list.

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