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

With no annotations, the description does carry some weight: it discloses the returned fields (workflow_id, name, nodes_count, deleted_at, source) and implies the results are soft-deleted, recoverable items rather than purged ones. It says nothing about ordering, pagination, limits, or whether items past a retention window are excluded — meaningful gaps for a list tool with zero annotation coverage.

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 line, front-loaded with the resource definition, and every clause carries information — the field list is genuinely useful since there is no output schema. It reads as an incomplete sentence fragment rather than a defined statement of behavior.

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 zero-parameter read tool with no output schema, the description supplies the key missing piece: what each returned record contains. What remains absent — pagination behavior and retention semantics — is modest but non-trivial for a recovery-oriented listing.

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?

The tool takes no parameters, so there is no parameter semantics to explain; the baseline is 4. The description doesn't confuse matters by implying hidden filters.

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 phrase "Deleted workflows that can be restored" clearly identifies the resource and its scope, and the appended field list shows it returns a collection. It lacks an explicit verb and never names a sibling (e.g., workflow_list for active workflows or pipeline_deleted_list), so differentiation is implicit rather than stated.

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 when-to-use guidance and no mention of the natural follow-up alternative, workflow_deleted_restore, even though "can be restored" points directly at it. The agent must infer from the name alone that this is the place to look before restoring.

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