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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, and the description reinforces with 'Does not run workflows.' It adds genuinely new context by disclosing which entries carry execution evidence (RSS example, OpenClaw staging-backup) and what remains untested (memory behavior, upgrade regressions) — useful trust signals not available elsewhere.

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 short sentences, front-loaded with purpose then routing then evidence caveats. The evidence sentence is longer than needed but every clause maps to real behavior; little waste.

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 purpose/routing/evidence are covered well. However, with 0% parameter description coverage the four filters go entirely unexplained, which is a real gap for an agent choosing query arguments.

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 0% across four parameters, yet the description never mentions the q, page, product, or language filters or what they constrain. The only hint is that list entries have a stable ID, which doesn't explain how to page, filter by product, or set language.

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 owned, reproducible workflow procedures,' and distinguishes the detail path by naming get_item for steps and versions. Clearly not the same as the search/catalog siblings, though it doesn't contrast against all of them.

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?

Explicitly routes agents to get_item for steps, pinned versions and verification limits, and closes with 'Does not run workflows' to exclude execution. It stops short of saying when to prefer this over botclaw_search or botclaw_get_catalog, so no full when/when-not matrix.

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