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

With no annotations, the description carries the full burden. It usefully discloses a non-obvious edge case — that a version is vulnerable when the only remedy is an isolated patch and fixedIn is then null — which is genuine behavioral context. But it says nothing about permissions, error behavior, or result shape beyond that one field.

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, each earning its place: purpose first, the fixedIn edge case second, and the routing trigger third. No filler and the core capability is front-loaded.

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 two-parameter read-only lookup with no output schema and no annotations, the description covers purpose, the key output-field nuance, and invocation triggers, which is close to sufficient. The main residual gap is that the overall response shape and any distribution-specific behavior are unstated.

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 coverage is 50%: version is documented in the schema while distribution has no description. The description frames 'version' as a Magento/Adobe Commerce version but adds no syntax, format, or distribution-selection guidance beyond the schema, so it neither compensates for the gap nor is fully redundant.

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 ('Check whether a specific Magento/Adobe Commerce version is vulnerable... and which version fixes it') and implicitly distinguishes itself from siblings like get_security_bulletins and find_patch by framing the operation around a specific version rather than listing bulletins or patches.

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?

Gives explicit routing cues with quoted user intents ('is my Magento vulnerable', 'which patch fixes CVE-...'), which is strong when-to-use guidance. It does not, however, name the alternatives (e.g., get_security_bulletin, find_patch) or state when not to use this tool, so it stops short of a 5.

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