Validate AI Operations Artifact

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

Annotations already declare readOnlyHint=true, and the description is consistent with a read-only validation operation. It adds context about the artifact types and draft version, but it does not disclose whether validation is structural, semantic, or what happens for invalid artifacts.

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?

One short sentence with no filler, front-loads the action, and every word adds specificity. This is an appropriate length for the available schema and annotation context.

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?

With no output schema and no description of return values or error behavior, an agent cannot predict what the tool will provide after invocation. The single-parameter schema is simple, but validation semantics and result shape are left unspecified.

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 schema describes artifact only as an object with 0% coverage, so the description's 'workflow or run artifact' adds meaningful type context. However, it still does not describe any expected fields or constraints inside the artifact object, leaving the agent with limited ability to construct or inspect it.

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 (validate), a specific resource (workflow or run artifact), and a target standard (AI Operations v0.4 draft). It does not explicitly distinguish itself from siblings like core.verify or lens.analyze_workflow, but the artifact-and-draft scope is distinctive enough.

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?

No guidance is given on when to use this tool versus core.verify or lens.analyze_workflow, and there are no exclusions or prerequisites. The only contextual clue is the spec namespace, which the agent must infer.

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