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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description contributes genuinely new behavior: results are restricted to the connected user's participation, and each entry carries handoff states plus a count of claimable tasks — useful signals that the annotations cannot convey. It stops short of describing ordering or empty-result behavior.

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?

Two sentences, both earning their place: the first defines the resource and its scope, the second covers response content and pagination. The scope constraint is front-loaded so an agent sees the key limitation immediately.

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?

For a single-optional-param read tool with no output schema and annotations covering read-only safety, this is close to complete: it explains the domain entity, the visibility filter, and the notable payload fields. Only minor gaps remain, such as result ordering and behavior when the user has no workflows.

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 100% and the single 'page' parameter is fully documented in the schema, including the next_page usage pattern and the 100-results-per-page size. The description's only contribution is the word 'Paged.', which adds nothing beyond the schema, so the baseline of 3 applies.

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?

The description gives a specific resource (workflows) with an inline definition of the domain term ('handoff chains between users') and an explicit scope: workflows the connected user takes part in. That scoping distinguishes it from list-style siblings such as gocanvas_list_dispatches, though it never names an alternative explicitly.

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?

Usage is implied by the scope clause ('the connected user takes part in') and by the promise of task counts ('tasks available to claim'), which hints at a work-queue use case. There is no explicit when-to-use guidance, no exclusions, and no pointer to a sibling when the user needs workflows they do not participate in.

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