Get Workflow

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that, and "Reads community data" is an inaccurate characterization of what is fetched, so it contributes no useful behavioral context.

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?

It is short and front-loaded, but the brevity stems from under-specification rather than economy — the second sentence is filler that conveys no actionable 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 simple id-based read this is under-developed: with no output schema, the description should at least say what a workflow object represents or what the call returns. Instead it supplies a misleading generic phrase and leaves the agent to infer the tool's role from the name alone.

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 both parameters (id, account) are documented in the schema, including the non-obvious note that account selects credentials rather than a remote community ID. The description adds nothing here, 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?

"Get Workflow" merely restates the tool name and title, and the only added clause — "Reads community data" — is vague and arguably misleading, since a workflow is not community data. It does not distinguish this tool from siblings like list_workflows, duplicate_workflow, or activate_workflow beyond the obvious singular/plural.

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?

No when-to-use guidance whatsoever: no statement that this is the single-record fetch to use when you already have a workflow UUID, and no mention of the list_workflows/duplicate_workflow alternatives. The agent must infer everything from the name.

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