validate_bpmn_xml

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

It states that the tool performs validation, which implies a read-only, non-destructive behavior, but it does not describe return values, error reporting, or any side effects. With no annotations provided, the description carries the full burden, so a bit more behavioral detail would be expected.

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?

A single sentence with no filler or redundancy. It is appropriately sized for a tool with no input parameters and is front-loaded with the action and target.

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 references validating an XML string, but the schema defines no input parameters, so an agent cannot tell how to pass the string. There is also no output schema or explanation of validation results. Given zero annotations and no schema support, the description is not sufficient to invoke the tool confidently.

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 input schema has zero properties, so the description cannot add per-parameter detail; the baseline for zero parameters is 4. The description does add meaningful context by identifying the input as an XML string for BPMN 2.0, though it does not name how that string is supplied.

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 uses a clear verb ('Valida') and a specific resource ('string XML BPMN 2.0'), so the core purpose is immediately understandable. It does not explicitly contrast with the sibling validate_bpmn_file, though 'string' hints at the difference.

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?

There is no guidance on when to use this tool versus validate_bpmn_file or the many process-creation tools. The intended usage is only implied by the tool name and brief description, with no exclusions or alternative recommendations.

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