md_export_xsd_to_car_mdf_checked

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

With no annotations, the description carries the full burden of disclosing behavioral traits. It mentions 'hash-bound' and 'audited' but does not explain side effects, permissions, idempotency, or the meaning of the dry_run and confirmation_token parameters. The tool likely creates or modifies files, but that is not explicitly stated.

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, efficient sentence with no wasted words. It is front-loaded with the primary verb and resource, making it easy to parse and remember.

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?

Despite having an output schema, the description is insufficient for a tool with eight parameters and no annotations. It fails to explain key concepts like 'hash-bound', 'audited', and how the parameters relate to the overall workflow, leaving the agent without enough context to invoke it confidently.

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 0%, and the description adds minimal meaning beyond the schema. The phrase 'hash-bound' hints at input_sha256, and 'audited' hints at confirmation_token, but these are not mapped to parameters explicitly. Most of the eight parameters, including dry_run, idempotency_key, and timeout_seconds, remain unexplained.

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 action ('Export') and the specific resource ('hash-bound project XSD') and output ('audited CAR/MDF pair'). This distinguishes it from sibling tools that perform other conversions or checks, such as md_convert_to_lammps_checked.

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, prerequisites, or conditions. It merely states what the tool does without any contextual or exclusionary information.

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