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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description usefully adds the sort order (most recently updated first), which implies the cursor semantics, but it says nothing about pagination behavior, page size limits, or what an empty result means.

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?

One short sentence with no waste and the key scoping and ordering facts front-loaded. It is efficient, though bordering on under-specified for a paginated list tool.

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?

With no output schema, a nested cursor object, and an undocumented limit parameter, the description leaves pagination mechanics and return shape entirely to inference. For a paginated listing tool this is a meaningful gap.

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 only 50% – limit has no description and only constraint keywords, and cursor carries a brief schema note. The description adds no parameter meaning at all, not even that the updatedAt/id cursor pairs with the stated sort order.

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 names the resource (workflows), its scope (the user's), and the ordering (most recently updated first), which lets an agent recognize it as a listing tool. It does not explicitly contrast itself with the singular sibling get_workflow, so it falls short of the top band.

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?

There is no guidance on when to use this versus get_workflow, create_workflow, or any other sibling; the agent must infer it from the name alone. Listing is the obvious reading, but no alternative or condition is stated.

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