run-data-contract-validation

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

The description adds that the tool is write-gated and that OM records validation results, indicating mutation. Without annotations, this is helpful but lacks details on side effects, permissions, or response behavior beyond the result.

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?

Two concise sentences that front-load the key action and result. No wasted words; every sentence contributes meaning.

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?

Missing details about the return format of the validation result, error handling, and how it relates to other data contract tools. No output schema is provided, so the agent lacks information on response structure.

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 coverage is 100% with descriptions for both parameters. The tool description does not add any parameter-level information beyond what the schema already provides, so baseline score of 3 is appropriate.

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 it triggers Data Contract validation and returns the official result. However, it does not differentiate from the sibling tool 'validate-data-contract', which may have similar functionality.

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 on when to use this tool versus alternatives like 'validate-data-contract' or 'get-data-contract-latest-result'. The mention of write-gating provides a condition, but no explicit when-not or alternative advice.

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