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

Goes well beyond the annotations: it discloses that the tool only stages XML in temporary memory and does not parse or compare yet, documents the success payload (status=OK, upload_id, cumulative received_chars), and names the two fatal error states. This adds real behavioral context that the hints alone (readOnlyHint=false, idempotentHint=false) do not convey.

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 action, then constraints, then return/error semantics, then scope caveat. Four dense sentences all carry information, though the ordering/no-overlap sentence is slightly packed.

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 exists, and the description compensates by describing return fields and error outcomes, plus the prerequisite (begin_nodeset_upload), the ordering contract, and the staging-only limitation. An agent has everything needed to invoke and interpret it correctly.

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?

With schema description coverage at 0%, the description carries the full burden and largely succeeds: upload_id must be exactly as returned by begin_nodeset_upload, and chunk is the next consecutive XML text segment with ordering/no-overlap constraints. It does not specify chunk size limits or encoding, leaving a small gap.

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+resource (append the next unmodified text chunk to a temporary NodeSet2 upload) and ties the tool to its creator sibling, begin_nodeset_upload. An agent can place it correctly in the upload workflow without opening the sibling schemas.

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?

Gives explicit sequencing rules (send every chunk in original order, no overlap/omission/reformatting) and explains which error codes mean the upload cannot continue. It does not explicitly name when to stop using this tool in favor of audit_uploaded_nodesets, but the workflow context is clear.

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