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

Annotations only declare readOnlyHint=false, idempotentHint=true, destructiveHint=false. The description adds substantially more: authorization rules (current assignee, org admin, admin override requires OAuth not --bot), optimistic-concurrency semantics via 409, and notification side effects (bot event plus email/Slack per user settings). This is richer behavioral context than the annotations carry.

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?

Dense but front-loaded: the action comes first, then eligibility, then failure handling, then side effects. A few clauses (notification mechanics) could be trimmed, but every sentence carries real information.

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?

Covers behavior, permissions, retry, and the return value ('Returns the updated execution'), which compensates for the absent output schema. The QA-bot path (botId/projectApiKey) is left entirely to the schema and never mentioned in the description, a minor gap at 83% coverage.

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 83%, so most params are already documented. The description restates that assignee/CC accept team member user ids or emails (which the schema already says) and adds only the self-removal nuance for CC. Baseline 3 is appropriate since the schema does the heavy lifting.

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 ('Change the assignee and/or CC list of a workflow execution'), distinct from read siblings like get-workflow-executions. The scope of mutable fields is stated immediately.

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 preconditions ('Only call after the user explicitly approved the change'), permission rules per caller type, the self-removal exception for CC'd users, and a concrete recovery path for 409 ('re-read with get-workflow-executions and retry'). This is exactly the when/when-not guidance an agent needs.

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