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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the description carries little behavioral burden — but it adds almost nothing either. It does not say what happens when the id doesn't exist (error vs empty), nor what a 'workflow' contains, leaving the description purely restating the call.

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 with zero filler — well formed for a simple fetch tool. It is terse to the point of under-specification, but that is better captured in other dimensions than as verbosity here.

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 one-parameter read tool with full schema coverage, complete annotations and no output schema, the description is minimally sufficient: an agent knows it fetches a single workflow by id. It still leaves unclear what a workflow record is or how failures manifest, which a slightly longer description could cheaply cover.

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% and the single parameter is documented as 'The workflow id.' The description repeats the id concept without adding format, provenance, or lookup hints beyond the schema, so the baseline 3 applies.

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 (workflow) with a singular scope ('one ... by id'), which naturally distinguishes it from workflow_list, workflow_create, workflow_update and workflow_delete. It does not name any sibling explicitly, so it stops short of a 5.

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: an agent can infer this is the tool for fetching a single known workflow id rather than enumerating them. There is no explicit when-to-use versus workflow_list, and no precondition such as 'id must come from workflow_list'.

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