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

Annotations already declare readOnly, idempotent, non-destructive, closed-world. The description adds genuinely new context: responses always use the same collection envelope regardless of arity, and includes must respect caps and report truncation/pagination. It doesn't cover auth/workspace binding, but the annotation bar is already met.

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?

Front-loads the core read behavior, then the id-count semantics, then the include contract. The final sentence ('Includes can add graph, stats...') partially restates include listings already present in the schema, making it slightly padded, but the rest earns its place.

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?

An output schema exists, so return values need not be re-explained, and annotations cover safety. The description still adds the envelope-stability and truncation contract, which is meaningful. Minor gaps remain around filter semantics, but the tool is adequately described for correct invocation.

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 50%, so the schema documents ids, limit, cursor, and each include. The description reinforces the ids semantics and the include caps/truncation contract, but adds little on the undocumented filters (status, enabled, campaignId, signalAgentId) or workspaceId behavior.

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?

States a specific verb ('Read') and resource ('workflows'), and clarifies the single-vs-many behavior. It does not name any sibling to distinguish against, but no sibling is a competing read-workflows tool (the near neighbors are edit_workflow/delete_workflow, clearly writes).

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?

Gives explicit conditional guidance: omit ids to list, pass one id for one record, several for several. Also advises using 'include' only for details the user asked for. Lacks any exclusion against an alternative tool, but the when-to-use conditions are clear.

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