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

Annotations already declare readOnly/idempotent/non-destructive/openWorld=false, so the safety profile is covered. The description adds genuinely new context: the shape of the returned payload (trigger, graph, schedule, runCount/maxRuns) and a plan-gate requirement for automations, which an agent needs before calling.

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 front-loaded sentence with no filler; the parenthetical field notation is compact. The terse bracket syntax ({event, condition}, {cron, timezone}) is efficient but borders on cryptic without a legend.

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 sketches the return structure, and the plan gate covers access requirements. It omits where a workflowId comes from (e.g., list_workflows) and any error behavior, leaving minor gaps for a simple single-parameter read.

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 0% and the single required parameter workflowId is undocumented in both the schema and the description. The description describes return fields rather than the identifier, so it fails to compensate for the coverage gap even though the parameter is largely self-evident from its name.

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+resource ('get_workflow' → 'Full workflow definition') and enumerates the constituent parts of what is returned. It does not distinguish itself from near-siblings like get_workflow_run, list_workflows, or design_workflow_draft, so an agent must infer the boundary from the name alone.

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 routing to alternatives; the only contextual note is the plan gate ('automations (PRO+)'), which is an access prerequisite rather than usage direction. The agent gets no signal on when to prefer this over list_workflows or get_workflow_run.

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