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

Annotations already declare readOnly, idempotent, non-destructive behavior, so the bar is lower. The description adds valuable behavioral context beyond annotations by stating that the local created-workflow policy is not applied, no steps execute, and no secrets are accepted.

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 three short sentences with no wasted text. The core operation is front-loaded, followed by important behavioral constraints, so every sentence earns its place.

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 tool has four parameters including a nested bundle object, no output schema, and 0% schema description coverage. The description omits nearly all parameter semantics and does not explain how bundle validation, kind selection, or format affects the check, so it is incomplete for an agent to invoke it correctly in non-default cases.

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 0%, so the description must carry parameter meaning, but it only implies the yaml input. It says nothing about the kind, format, or nested bundle parameters, leaving the agent to infer their purpose entirely from the schema structure.

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 a specific verb and resource: a format check of workflow YAML using the bundled Q-Core validator. It is clear enough to distinguish validation from execution, but it narrows the scope to workflow YAML and never mentions component manifests or JSON despite the kind/format parameters, and it does not differentiate from sibling tools.

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 implies usage for format checking and usefully clarifies that local created-workflow policy is not applied, no steps run, and no secrets are accepted. However, it does not explicitly say when to use this tool versus alternatives like schema or instructions, nor does it state exclusions for component or JSON validation.

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