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

With no annotations, the description carries the full burden, and it delivers: list mode can return hundreds of hits, ranked mode returns a 0-100 score plus matched signals, Mage-OS always yields status 'unknown', and includeInapplicable keeps the real applicable flag. It still omits auth/permission requirements and pagination behavior, so it is strong but not exhaustive.

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?

Four dense sentences, front-loaded with the core purpose before the ranking mechanics and the two caveats (security routing, Mage-OS). Nothing is wasted, though the long middle sentence packs several ideas together.

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?

No output schema exists, yet the description explains the return shape (ranked list, relevance score, matched signals, applicable flag), the volume risk, and the Mage-OS edge case. An agent has everything needed to invoke it correctly.

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 86%, so the baseline is 3, but the description adds real meaning: query accepts symptoms, error text, feature words, or a patch id (ACSD-56760); modules take names with or without the magento/module- prefix; categories are QPT names. It also clarifies that query/modules/categories switch the tool into ranked mode, which the schema alone does not convey.

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 (find QPT patches) scoped to a Magento Open Source or Adobe Commerce version, and immediately separates itself from the sibling check_version_security. An agent can tell what this tool owns without opening the 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?

Gives explicit when-to-use branches: bare distribution+version = full list; adding query/modules/categories = ranked list; security fixes = use check_version_security instead. It also warns that Mage-OS is not a valid QPT target, which prevents a wasted call.

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