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

Annotations only declare generic hints, but the description adds operational constraints the agent cannot get anywhere else: 15-minute upload expiry, a maximum of four concurrent uploads, in-memory-only storage, and no external system modification. It also discloses the return payload (upload_id, max_total_chars) that subsequent calls depend on.

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?

Purpose and the trigger condition are front-loaded, followed by the workflow, then return values, then limits and side-effect profile. Four sentences, each carrying distinct actionable information with no repetition of the schema or annotations.

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?

Even without an output schema, the description explains what is returned and why it matters, and covers lifecycle (expiry), throughput limits (four active uploads), and statefulness. An agent has everything needed to initiate the upload flow 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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless tool is 4. The description usefully documents the values this call produces (upload_id, max_total_chars) even though it does not need to explain any inputs.

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 ('Start one temporary in-memory upload for a large NodeSet2 XML document') and names the exact condition that creates the need (documents too large for audit_nodeset_compatibility). An agent can distinguish this from append_nodeset_chunk and the audit tools without reading any schema.

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 when-to-use ('when the complete XML documents are too large for audit_nodeset_compatibility'), the calling pattern ('once for the old baseline and once for the new candidate'), and hands off to the named next step, append_nodeset_chunk. No alternative selection is left to inference.

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