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

With no annotations, the description carries the full burden. 'Fetch' implies a read, but it says nothing about what happens when no prior run exists (critical for a 'last run' tool), auth requirements, or pagination. The only behavioral hint is the 'since-last-run scoping' use case.

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?

Two tight sentences with the core action front-loaded and no filler. Efficient, though the parenthetical is slightly dense.

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?

For a simple read tool with no output schema and no annotations, the description covers the core action and parameter roles but omits edge-case behavior (no-run-found) and any return-shape hint, leaving real gaps given 0% schema coverage.

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 0%, so the description must compensate, and it does map all three params: workflow-id, branch, and the optional userId 'for per-user last run'. It clarifies meaning but adds no format, syntax, or default details.

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?

States a specific verb and resource ('Fetch the last workflow execution') and qualifies it by workflow-id and branch, which is enough to separate it from list-workflow-executions and get-workflow-execution. However it never explicitly names the sibling it differs from or explains the 'last' scoping relative to those tools.

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 trailing clause 'Used for since-last-run scoping' gives a usage context, but there is no when-to-use-vs-alternatives guidance, no exclusions, and no mention of when to prefer list-workflow-executions or get-workflow-execution instead.

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