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

Annotations already establish that this is a safe, read-only, closed-world check. The description adds meaningful scope: it only checks the draft, returns issue codes and JSON Pointer paths, and is not a substitute for real testing. It does not describe pagination or output structure in detail, but for a simple validation tool this is adequate.

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 short and front-loads the core behavior, exclusions, next step, and limits. The telegraphic sentence fragments are efficient but slightly choppy, and the example at the end is useful without being wasteful.

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, read-only validation tool, the description covers what it does, when to use it, what not to use it for, the next step, and a usage example. The only mild gap is that the exact shape of returned issues is not described, though the mention of codes and JSON Pointer paths gives enough orientation.

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 100% and there is only one required parameter, so the schema already explains workflowId fully. The description adds a concrete example call, but no further semantics about the parameter beyond what the schema provides.

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 states the tool lists workflow issues with codes and JSON Pointer paths, which is concrete and recognizable. It distinguishes itself from a real test and points toward workflow_guard, though the opening verb 'List' is less direct than 'Validate' for a tool named workflow_validate.

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?

It explicitly says to use the tool when a draft changes and explicitly says not to use it as a real test, which is useful exclusion guidance. The next step is also named: fix issues, validate again, then call workflow_guard. The actual alternative for real testing is implied rather than named.

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