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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=false, so the safety profile is covered. The description adds that it returns a run ID and 'queued status,' revealing async behavior, but never acknowledges that triggering can be destructive or that repeated calls spawn separate runs. With annotations present, a 3 is appropriate.

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 sentences, front-loaded with the action and resource, then return behavior, then the usage cue. Every sentence contributes; no filler.

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 one-parameter async trigger with no output schema and annotations covering safety, the description covers purpose, return value, and usage context. It could go further by pointing to job_status for polling the queued run, which is the obvious next step for an agent.

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?

The single parameter has 0% schema description coverage, so the description must carry the load. It clarifies that 'id' is the saved workflow's identifier (not a run ID) and that a user may reference it by name, which adds real meaning. It still does not define the ID format or where to obtain it.

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 ('Trigger') and resource ('saved PDFLean workflow/pipeline by its ID') and clarifies that workflows are pre-created in the web app. No sibling tool overlaps with workflow execution, so an agent can distinguish it immediately.

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 says 'Use this when the user references an existing workflow by name or ID,' which is a clear selection condition. It also implies workflows cannot be created here (they come from the web app), but it names no alternative tool or when-not condition.

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