test-workflow

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

Given no annotations, the description fully discloses behavior: automatic trigger detection, different testing mechanisms, return of structured results with AI-friendly error diagnosis, and a crucial formatting requirement (compact, single-line JSON).

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 description is concise with bullet points for different trigger methods. Every sentence adds value, and the important note about JSON format is prominently placed. 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?

The description covers core functionality, parameter usage, return format, and special requirements. With no output schema, it explains return values. For a 6-parameter tool, it provides sufficient context for correct 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 coverage is 100%, so baseline is 3. The description adds value by explaining the JSON formatting strictness, the purpose of 'autoConvert' for manual/schedule triggers, and the default for 'testRunnerPath', which goes beyond the schema's basic descriptions.

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 'Universal workflow testing tool' and explains how it adapts to different trigger types (webhook, sub-workflow, manual/schedule). This distinguishes it from siblings like 'execute-webhook' and 'activate-workflow'.

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 description provides explicit guidance on when to use each testing method based on trigger type. However, it does not directly contrast with alternatives like 'execute-webhook' or state when not to use this tool.

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