validate_adf_artifacts

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It describes what the tool does (validates for structural correctness) and what it returns (list of issues or success message), but doesn't mention error handling, performance characteristics, permission requirements, or whether it modifies files. It provides basic behavioral context but lacks depth.

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?

Three sentences with zero waste: first states purpose, second specifies validation criteria, third describes return behavior. Every sentence earns its place by adding distinct information. The description is appropriately sized and front-loaded with the core functionality.

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 single-parameter validation tool with no annotations and no output schema, the description provides adequate context about what it validates and what it returns. It could be more complete by specifying validation error formats or success message structure, but covers the essential functionality given the tool's relative simplicity.

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%, so the schema already documents the single parameter. The description adds minimal value beyond what the schema provides, only reinforcing that it's for 'generated ADF JSON artifacts' without adding format details or constraints. Baseline 3 is appropriate when schema does the heavy lifting.

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 clearly states the specific action ('validate'), target resource ('ADF JSON artifacts in a directory'), and scope ('structural correctness'). It distinguishes from siblings by focusing on validation rather than analysis, conversion, deployment, or scanning operations.

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 context (when you need to check ADF JSON artifacts for structural issues) but doesn't explicitly state when to use this tool versus alternatives. No guidance is provided about when NOT to use it or what specific scenarios warrant validation.

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