get_workflow

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

With no annotations, the description should disclose behavioral traits. 'Get details' implies a read operation, but it does not confirm idempotency, auth requirements, or side effects. The description fails to provide sufficient behavioral context beyond the implied retrieval.

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 description is concise (two sentences) with no redundant information. It follows a standard docstring format with an args section. While compact, it sacrifices completeness for brevity.

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?

Given no output schema and no annotations, the description does not inform about the response structure, pagination, or any details beyond the fact that details are returned. This is insufficient for an AI agent to know what to expect from the 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?

The description adds minimal value over the schema, simply restating 'workflow_id' and labeling it as 'UUID'. Since schema coverage is 0%, the description should compensate by explaining the parameter's format, source, or constraints, which it does not.

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 clearly states the verb 'Get' and resource 'workflow', indicating retrieval of details for a specific workflow. It is distinguishable from sibling tools like list_workflows (which lists) and get_workflow_version (which targets a different resource). However, it does not elaborate on what 'details' entails, which could leave ambiguity.

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 usage guidance is provided. The description does not specify when to use this tool over alternatives, such as list_workflows or get_workflow_version. It lacks any context about prerequisites or scenarios where this tool is preferred.

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