get_workflow_result

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

The description discloses that the workflow must be completed, which is a key behavioral constraint. However, it does not specify what happens if the workflow is not completed (e.g., error or empty result) or describe the output format. Without annotations, more detail would be beneficial.

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 a single short sentence, which is concise and front-loaded. It effectively states the core purpose, though it could be slightly expanded with usage context without losing conciseness.

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 the tool has no output schema and no annotations, the description is too minimal. It does not explain what the result contains, error behavior, or how it differs from similar tools like get_workflow_history. More detail is needed for adequate completeness.

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 has 100% description coverage for the single parameter, so the description does not need to add much. However, it adds no extra meaning beyond the schema, such as how to obtain the workflow ID or expected format.

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 'Get the result of a completed workflow' clearly states the verb (get) and resource (result of a completed workflow). It distinguishes from siblings like get_workflow_history and get_workflow_event, which serve different purposes.

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?

The description implies the tool should be used only for completed workflows, but it does not explicitly state when to use it versus alternatives like get_workflow_history or query_workflow. No when-not-to-use or alternative tool names are provided.

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