XML format / minify / validate / to JSON

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

Goes beyond the readOnly/idempotent annotations with real behavioral detail: no external DTD or entity loading (a meaningful side-effect guarantee), fidelity guarantees that mixed content, CDATA and xml:space="preserve" are kept as written, and that validation errors carry line/column. It does not say what validate returns on success or how large outputs are handled in the reply, but the added context is substantial.

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?

Front-loaded with the four modes and their distinguishing behavior, then input guidance. Dense but every clause carries information; the trailing web-version URL is the only low-value element.

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?

For a 6-parameter tool with no output schema and readOnly annotations, the description covers modes, input sources, preservation behavior, and safety limits. Remaining gaps (success return shape for each mode, behavior on invalid XML in non-validate modes) are modest and partly covered by the schema's 'validate never throws' note.

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 100%, so all six parameters are already documented in the schema, which sets the baseline at 3. The description adds little parameter-level meaning beyond restating the indent options and input source; the '@name'/array/'#text' notes describe JSON conversion output conventions rather than parameter behavior.

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?

Specific verbs and resource: validate (with well-formedness/namespace checks), pretty-print, minify, convert to JSON — an agent immediately knows the four modes. It does not name xml_query, the closest sibling that also operates on XML, so the boundary between 'format' and 'query' work is left implicit. Still clearly distinguishable from html_format/json_format by the XML resource.

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?

It gives input guidance ('Give "text" or a file "path"') and mode-level semantics, so usage is implied rather than stated. There is no explicit when-to-use/when-not guidance and no pointer to xml_query for query-type work. Adequate but leaves the agent to infer tool selection.

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