getWorkflowExecution

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the completion-state semantics, which is useful beyond the annotations. However, it doesn't disclose return shape, pagination, or how results are structured per step, leaving some behavioral gaps for a read tool with no output schema.

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?

Three short sentences, front-loaded with the resource identity, followed by usage and completion semantics. Every sentence contributes.

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?

Complete enough for a read-only retrieval tool whose annotations cover safety and whose two params are fully documented in schema. Without an output schema and with a per-step result payload, the description could say more about the return structure, but the essential calling context is present.

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 coverage is 100%, so the baseline is 3, but the description adds meaning by explaining execution_id as coming from testWorkflow – a provenance hint the schema also touches on. It doesn't add syntax detail beyond the schema, keeping it modestly above baseline.

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 states a specific resource ('one run of a workflow, with the result of each step') and a concrete use ('read the outcome of testWorkflow'). It clearly distinguishes itself from getWorkflow and testWorkflow in the sibling list.

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?

Names the action it pairs with ('read the outcome of testWorkflow') and gives the terminating condition for use ('a run is finished when state is completed, failed or cancelled'). This routes the agent from testWorkflow to this tool for retrieving results.

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