run_workflow

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

No annotations provided, so description carries full burden. Discloses cost, supported services, interpolation syntax, and output (final + intermediate). Does not mention potential side effects or idempotency, but tool appears read-only.

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?

Four sentences front-load the key purpose and cost, then detail function and example. No wasted words.

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?

Covers all necessary aspects: steps limit, service list, syntax, cost, output type. No output schema but description says what is returned. Context signals show 2 parameters with 100% schema coverage, so description is complete.

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%. Description adds significant meaning: the $"from" syntax for passing outputs, list of supported services, cost, and a concrete example. This goes well beyond the raw schema.

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 'Chain multiple Boltwork services in a single call', specifying a pipeline of up to 5 steps. This distinguishes it from sibling tools like 'summarise_webpage' or 'translate' which are individual services.

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?

Explicitly mentions when to use (chaining services) and provides an example. Includes cost (1000 sats) which aids decision-making. Lacks explicit 'when not to use' or alternative suggestions, but context is clear.

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