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

Annotations declare destructiveHint=true, readOnlyHint=false and non-idempotent; the description corroborates this by stating the call consumes both upload IDs and warns against reuse — precisely the destructive/write behavior an agent must anticipate — and further discloses the report shape since no output schema exists.

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-loads the comparison purpose, then prerequisites, then the consumption warning, then the return shape, then the alternative. Every sentence carries distinct operational information with no filler.

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?

With no output schema, the description supplies the result enum values, counts, issue structure and summary fields, and it covers prerequisites, ID consumption, and the sibling fallback. Nothing an agent needs to select or invoke it correctly is missing.

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%, so the schema offers only bare titles. The description compensates by defining old_upload_id as the baseline revision and new_upload_id as the candidate revision, which is the essential semantic distinction, though it adds no format/source detail about the IDs themselves.

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 and resource ('Compare two large NodeSet2 XML revisions') plus the scope constraint ('large', post-staging), which cleanly separates it from the sibling audit_nodeset_compatibility that handles small in-request documents.

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?

Explicitly names the prerequisite workflow (begin_nodeset_upload + append_nodeset_chunk), says which ID goes where, and gives an explicit alternative condition: 'Use the direct audit tool instead when both complete XML documents fit in a single request.'

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