nds_mutation_verify

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It does not mention whether the operation is read-only, has side effects, requires specific permissions, or describes failure outcomes. The word 'revalidate' implies verification but adds no concrete behavioral detail.

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 a single, focused sentence with no filler, putting the verb 'revalidate' up front. It is appropriately concise, though the heavy use of domain jargon (e.g., 'deterministic NDS mutation build') may obscure clarity for agents unfamiliar with the domain.

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?

Given there is no output schema or annotations, the description should at least hint at return values or success/failure criteria, but it does not. It also fails to explain the relationship with sibling tools like nds_mutation_build and nds_mutation_validate, leaving the tool's role in the broader workflow unclear.

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 description coverage is 0%, so the description must compensate. It mentions 'workspace manifest' but does not explain the 'rom' parameter or how the two parameters relate. No format, constraints, or role of each parameter is described, leaving the agent to infer meaning from parameter names alone.

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 uses a specific verb 'revalidate' and identifies the resource as 'the exact deterministic NDS mutation build derived from a strict workspace manifest', which clearly states its purpose. However, it does not explicitly distinguish from sibling tools like nds_mutation_validate, so it is clear but not fully differentiated.

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 explicit guidance is provided on when to use this tool vs alternatives such as nds_mutation_validate or nds_mutation_build. The phrase 'freshly revalidate' hints at a re-check use case but does not offer exclusions or mention alternative tools, leaving the agent without clear selection criteria.

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