mesa_datacite_export

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

With no annotations, the description carries the full burden, and it does disclose the two output serializations and the DataCite schema version. However, it omits whether the operation is side-effect free, what happens with malformed or non-canonical AVUs, and whether validation occurs during export.

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?

A single sentence with the action front-loaded and no filler; the parenthetical adds the use case compactly. It is appropriately sized for a two-parameter transformation tool.

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?

No output schema and no annotations, so the description must carry everything. It covers the output format dimension adequately but leaves the agent without guidance on sequencing with sibling validate/template tools or on failure behavior.

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 50%: the avus parameter is documented in-schema but format has no description. The description compensates partially by naming both xml and json outputs, matching the enum, but adds no detail on how AVU attribute/value/unit map into the emitted document.

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?

States a specific verb ("Export") and resource ("DataCite AVUs") plus the two concrete output artifacts (DataCite 4.x XML, REST JSON), which is far more informative than the bare tool name. It does not explicitly name or contrast with siblings like mesa_datacite_validate or mesa_datacite_template, so an agent must infer the boundary.

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 parenthetical "(for DOI registration)" implies a use case for the XML format, but there is no explicit when-to-use, when-not-to-use, or named alternative. Nothing tells the agent whether to validate first with mesa_datacite_validate or to prefer this over mesa_datacite_template.

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