Create Upload Structure

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

Annotations declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=true, so the mutation and non-idempotency are already signaled. The description adds no extra context — it does not say whether data is persisted, what permissions are needed, or what the caller receives back.

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 efficient, front-loaded sentence with no filler. It is under-specified rather than bloated, which is a completeness problem rather than a conciseness one.

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 creation tool with no output schema, the description leaves critical gaps: what the result is, whether it must be passed to a subsequent upload call, and how it differs from the sibling upload creators. The annotations and rich schema cover part of the burden but not this routing/return-value context.

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% and covers all six parameters including nested page fields (pageNr, fileName, pageXmlName) with examples, so the schema does the heavy lifting. The description contributes nothing beyond it, so the baseline 3 applies.

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 verb (Create) and a resource (upload document structure describing pages), which is concrete, but 'structure' is ambiguous — it is unclear whether this builds a payload descriptor or persists an upload entity, and it is not distinguished from siblings such as upload_create_from_mets, upload_create_s3, or upload_page.

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?

No when-to-use guidance at all: no mention of prerequisites (collection must exist, files must be staged), no indication of the downstream call this structure feeds, and no exclusions relative to the other upload_* tools.

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