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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuinely new context beyond them: exactly which fields are returned and the explicit guarantee that credentials are never included, which matters for handling sensitive data. It stops short of describing behavior for a missing or unnamed workflow.

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: action first, contents second, security guarantee last. Every clause carries information and nothing is repeated from the title or schema.

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, the description usefully enumerates the returned fields (description, prompt, model, files, connections, limits, input_schema, output_schema) plus the credentials exclusion, which is enough to decide whether a follow-up call is needed. It omits error/not-found behavior for an unknown name, a minor gap for an otherwise simple read tool.

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% for the single `name` parameter, so the schema already documents it fully. The description's phrase "saved workflow's definition" reinforces that the name identifies an existing workflow, but adds no format, casing, or lookup-resolution detail beyond the schema.

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 and resource ("Read a saved workflow's definition") and enumerates the fields returned, so the agent knows this is the full-record fetch rather than a listing. It implicitly contrasts with list_workflows, but never names that sibling explicitly, so differentiation is inferential 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?

Usage is only implied: "Read a saved workflow's definition" suggests looking up a single known workflow by name, but there is no explicit when-to-use, when-not-to-use, or alternative (e.g. list_workflows to find a name first). No prerequisites are mentioned.

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