get_workflow

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only repeats the core idea of fetching details and adds no information about response shape, errors, permissions, or whether the operation is read-only. There is no value beyond the tool's name and obvious purpose.

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?

The single sentence is tightly written, front-loaded, and contains no filler. It uses only a few words to communicate the resource type and action, which is appropriate for a simple two-parameter retrieval tool.

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 annotations and no output schema, the description is thin. It tells the agent the action and resource, but does not indicate what 'details' will be returned, how to discover a workflow name, or what makes this endpoint distinct from related workflow and instance tools. The simple parameters help, but the surrounding context is incomplete.

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?

The input schema fully documents both parameters (account_id and workflow_name) with 100% coverage, so the description does not need to add much. It adds no extra context about naming conventions, id formats, or relationships between the parameters, but the schema already covers the essential semantics.

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?

The description names a specific verb ('Get') and a specific resource ('Workers Workflow'), which clearly distinguishes it from list operations like list_workflows and from get_workflow_instance. It is concise and identifiable, though it does not explicitly contrast with the workflow-instance variant.

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 guidance about when to use this tool instead of list_workflows, get_workflow_instance, or list_workflow_instances. No preconditions, exclusions, or alternatives are described.

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