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

Annotations already cover the safety profile (read-only, idempotent, closed-world, non-destructive), but the description adds substantive context beyond them: no model is invoked, the basis is 'patterns', and results carry confidence 'low'. That materially changes how much an agent should trust the output, which is the kind of disclosure annotations cannot express.

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 sentences, front-loaded with the core purpose and immediately scoped. The a-to-mind.com sentence is marginally promotional but does convey that the engine matches the public site, so it mostly earns its place; the confidence disclosure is well placed at the end.

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 carries the return-value burden and does so partially, disclosing that the structured result reports basis 'patterns' and confidence 'low'. Combined with 100% schema coverage, an agent has enough to call the tool correctly, though the shape of the findings list itself is not described.

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 all three parameters are already documented, making 3 the correct baseline. The description re-frames the schema's semantics ('pasted code or a diff's added lines', 'in many languages') but adds no syntax, format or precedence rules, such as what happens if both code and diff are supplied.

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 (pattern checks for bugs, risks and style) and resource (pasted code or a diff's added lines), plus a language scope. It also carves out its boundary against review_code_closer by declaring 'No model; the closer read is not included', so an agent can tell the instant check apart from the deeper one without opening either schema.

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 establishes this is the 'instant' pattern-based check and explicitly notes the closer read is excluded, which implies when it is the wrong choice. However, it never names review_code_closer or states the condition that should route the agent to it, leaving the selection rule to inference.

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