ms_geology_assess_nanopore_contract

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

With no annotations, the description carries the full burden. It adds a meaningful behavioral trait: 'fail-closed validate' and 'read' imply non-mutating, safety-oriented behavior. However, it does not explain what fail-closed means in practice (e.g., errors on missing data), nor does it disclose side effects, permissions, or output behavior beyond the existence of an output schema.

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, front-loaded sentence that states the action and object with no filler. Every word contributes meaning, making it highly concise and well-structured.

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?

The output schema exists, so return details are not required. However, the description lacks usage guidance and parameter semantics, which are essential for the agent to correctly invoke the tool. It is adequate for a simple one-parameter reader but incomplete in contextual decision-making.

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 only parameter, contract_path, has no schema description (0% coverage). The tool description adds context that the path points to a mineral nanopore construction contract, but does not clarify the expected format, whether it is a file or directory, or any constraints. The description provides minimal added value over the schema's title.

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 ('read and fail-closed validate') and identifies the resource ('mineral nanopore construction contract'), clearly distinguishing this tool from sibling tools that focus on building or packing structures. It fully explains what the tool does.

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 provides no guidance on when to use this tool versus alternatives, and does not mention exclusions or prerequisites. Siblings like md_project_validate or md_structure_preflight could overlap, but the description does not differentiate or offer selection advice.

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