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

Beyond the annotations, the description explains the reservation binding archive bytes and ownership, the no-storage-key/no-provenance rule, fork semantics, update preconditions, asynchronous job behavior, and authorization constraints. These are meaningful operational details for a non-read-only import tool.

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?

The description is dense but front-loaded and largely waste-free, covering requirements, constraints, update semantics, and the follow-up job tool. It is appropriately sized for a complex import operation, though it is packed enough to read as a single compressed block.

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?

Given the tool is a complex mutating import with an output schema, the description supplies the missing operational context: required inputs, forbidden inputs, fork vs update behavior, authorization scope, asynchronous job handling, and what to read from the resulting job. No essential call-time information 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 coverage is only 50% and the body is nested, but the description carries most of the semantic burden: it explains uploadId, idempotencyKey, optional destinationSlug/name behavior, expectedVersion and expectedDocumentSha256 preconditions, and forbids irrelevant storage/provenance fields. The commandId parameter is left to the schema description.

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?

The description states a specific verb and resource: importing an uploaded portable template package. It distinguishes this from sibling operations by naming the upload reservation, the optional fork behavior, the job handoff, and the related package/export tools.

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 explicit usage rules: use only uploadId and idempotencyKey, never supply storage keys or document bodies, optional destinationSlug/name forks, updating an existing slug requires expectedVersion and expectedDocumentSha256, and the caller should poll get_template_job until ready. It also states that project-bound editor credentials are refused.

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