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

Annotations already declare readOnly, idempotent, non-destructive. The description adds real value beyond them: entries carry stable IDs, the verification boundary lives in get_item, and only the Node RSS example currently has execution evidence — an honesty caveat about coverage that annotations cannot convey.

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 terse sentences, each earning its place, with the scope and the 'does not run' boundary front-loaded. No 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?

An output schema exists, so return values needn't be described, and the description covers scope and the get_item handoff. However, with 0% parameter coverage and a queryable/filterable list, an agent is left guessing about filtering and pagination semantics.

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 0% and there are four parameters (q, page, product, language), including two enums and a pagination default. The description says nothing about how to search, what q matches, pagination behavior, or what the enum values mean, so it fails to compensate for the coverage gap.

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+resource: 'Find owned, reproducible workflow procedures', and adds the boundary 'Does not run workflows.' It routes to the sibling get_item for steps, which helps distinguish it from retrieval tools, though it doesn't contrast with siblings like get_catalog or search.

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 a clear when-to-use path: list first, then call get_item for steps and the verification boundary. It also states the exclusion 'Does not run workflows.' No explicit guidance on the q/product/language filters, but the workflow (list → get_item) is unambiguous.

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