fetch_workflow_history

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

No annotations are present, so the description bears the full burden of behavioral disclosure. It only says this is a convenience method that fetches 'complete workflow history' and is similar to another tool; it does not explain the meaning of 'complete', what is returned, which run is used by default, or any error/edge-case behavior. The schema mentions 'latest run' but the description itself is vague.

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 definition is appropriately short and front-loaded: the first clause states the core action, and the second sentence provides routing guidance. The hedge 'may be easier' and the undefined 'workflow handle' add mild ambiguity, but no sentence is wasted.

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 output schema, no annotations, and no return-value description, the agent is left to infer what 'complete workflow history' actually contains. There is also a potential ambiguity between 'complete workflow history' and the schema's fact that only the latest run is fetched when runId is omitted. The description does not resolve this, making it incomplete for safe invocation.

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%, so the baseline is 3 even without parameter detail in the description. The description adds little beyond identifying workflowId as the ID-based handle, and its 'workflow handle' wording is somewhat inconsistent with the actual parameter name. The schema already documents runId and region well.

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 clear action and resource: 'fetch complete workflow history' and distinguishes this from get_workflow_execution_history by positioning it as easier 'when you only have the workflow ID.' However, the phrase 'using the workflow handle' introduces an undefined term that the schema calls workflowId, which slightly weakens the otherwise specific purpose.

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?

It explicitly names the closest alternative, get_workflow_execution_history, and gives a use-case condition for choosing this tool: 'easier to use when you only have the workflow ID.' It does not state when not to use it or describe exclusion cases, but the guidance is clear enough for routing.

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