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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is known. The description adds meaningful lifecycle behavior beyond that: results serve as a baseline, profiles persist for regression, and verification flows through verify_task. It still doesn't say what environment changes the run causes or what permissions are needed for an open-world execution, so it falls short of a 5.

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 short sentences with the capability, the prerequisite read, and the downstream chaining, in priority order. No filler; the alternative-tool routing is packed into a single clause.

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-value explanation is unnecessary, and the description covers selection, prerequisites, and follow-up. The remaining gap is behavioral detail for an open-world, non-read-only execution (what the playbook touches, resource cost), which keeps it at 4.

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 60%, so some compensation is expected; the description explains that profileId (or the returned result) acts as a baseline for verify_task, giving semantic meaning the schema's 'reuse a verification profile' line only hints at. async and responseMode remain undocumented in both places, keeping it below 5.

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?

Opens with a specific verb + resource ('Run a skill playbook') and gives concrete examples of playbook families (ship-gate, production-readiness-gate, SEO audit). It also explicitly positions itself against siblings load_skill and invoke_tool, so an agent can select it without inspecting schemas.

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 an explicit preference rule ('Prefer over load_skill or invoke_tool') and a concrete follow-up workflow ('After host fixes, verify_task with this result as baseline (or profileId)'). It even orders prerequisite reading (verification.evidence + loop.line first), which is actionable selection guidance rather than vague context.

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