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

The annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds useful context about the shape of returned data (per-message rows with client and exact text), but says nothing about ordering, the time window that 'Recent' covers, or pagination behavior beyond the unused limit parameter.

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?

A single front-loaded sentence that states what is returned before the optional filter, with no filler. Every clause adds 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?

For a two-parameter read tool with no output schema, the description does well to enumerate the returned fields. It is still incomplete on the semantics of 'Recent' (what window) and on the limit parameter, which an agent would need to choose a sensible value.

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 0%, so the description must carry the load. It explains workflowId ('filter to one workflow') but says nothing about limit — whether it caps messages, runs, or days — despite the schema exposing only a bare default of 30 and a maximum of 200.

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?

It names a specific resource (workflow runs/messages) and states exactly what each row contains: sent, drafted, or failed messages plus client and text. This clearly separates it from list_workflows (definitions) and list_workflow_approvals, though neither sibling is named 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?

The phrase 'optionally filter to one workflow' implies a usage pattern, but there is no explicit when-to-use guidance, no exclusion ('use X instead when...'), and no mention of how this differs from list_workflow_approvals or list_workflows.

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