dev_pipeline_validate

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description corroborates this by promising no execution. It goes further to enumerate the constructs it validates (variable capture, conditions, retryUntil polling, locks, explicit runners), giving the agent a real sense of validation scope.

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 front-loaded sentence with no filler; the non-execution qualifier appears at the end where it lands with impact. Dense but not padded.

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 tool validating a 256-node DAG schema with many nested options and no output schema, the description omits what a validation result contains (error list, schema violations) and how failures are reported. Adequate but leaves meaningful gaps.

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?

With 0% schema description coverage on a deeply nested pipeline object, the description must carry the burden. Its feature list (capture, conditions, retryUntil, locks, runners) loosely maps to nested fields but gives no syntax, constraints, or guidance on the deviceId/deviceName parameters.

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 (validate) and resource (persistent task DAG) and adds the crucial scope qualifier 'without executing it.' This implicitly separates it from execution siblings like dev_pipeline_start, though it never names an alternative explicitly.

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 phrase 'without executing it' implies this is a dry-run/pre-flight check, but the description never states when to prefer it over dev_pipeline_start or what a passing/failing result should trigger. Usage is inferable but not spelled out.

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