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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds useful behavioral context by explaining the band taxonomy and cursor-based pagination, though it repeats 'Read-only' and does not discuss auth or rate limits.

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?

The description is front-loaded with the core purpose, then quickly explains bands, workflow identification, filtering, and pagination. Every sentence contributes to correct invocation, and the final 'Read-only' note is brief and useful.

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?

The tool has an output schema and rich annotations, and the description fills the remaining gaps an agent needs: band meanings, workflow identification by ID or exact title, filtering, and cursor pagination. Nothing critical for selecting or invoking the tool is missing.

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 100%, so the baseline is 3, but the description adds meaningful semantics by enumerating the watch-list and collect-list band values, which the schema itself does not list as enums. It also clarifies that title is an alternative to workflowId and that cursor is the previous nextCursor.

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 states a specific verb and resource: paging through a workflow's work list kept between runs. It also distinguishes the operation from the mutation sibling update_work_list by explicitly calling this read-only, so an agent can identify the intended tool without opening 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?

It gives concrete invocation guidance: identify the workflow by workflowId or exact title, filter by band or query, and pass nextCursor as cursor for the next page. It does not explicitly name alternatives such as get_workflow or update_work_list, but the read-only paging context is clear.

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