List workflows

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so safety is covered. The description adds that provider scopes, locks and credits apply, which is genuine behavioral context, but it is boilerplate-generic and omits return shape or pagination behavior.

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?

It is short, but a large share of its wording ('Current Bannerbear V5 operation; provider scopes, locks and credits apply') is generic boilerplate that adds little. Front-loading the endpoint is reasonable but value-per-sentence is low.

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 2-param list tool with annotations covering the safety profile and no output schema, the absence of return/pagination description is a real gap but not fatal. The definition is minimally complete rather than thorough.

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 only 50% – 'account' is documented but 'page' has no description. The description contributes no parameter meaning at all, so it does not compensate for the undocumented pagination parameter or clarify iteration behavior.

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 reduces to the raw endpoint 'GET /v5/workflows', which implies retrieval of workflows, and the title/name carry the actual meaning. It does not articulate purpose in natural language or distinguish this from siblings like get_workflow or list_workflow_runs. Adequate but leaning on the title rather than stating a clear verb+resource intent.

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?

'Read operation' gives no when-to-use information, no alternatives (e.g., get_workflow for a single item, list_workflow_runs for executions), and no pagination guidance. The agent is left to infer everything from the name.

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