Shipping_getCollectionForm

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It adds only a vague execution-environment note ('Runs in your Kuudo deployment, not here') and does not disclose output format, side effects, idempotency, permissions, or whether reprinting consumes or modifies anything.

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 short, but the first sentence 'Catalog entry' is unhelpful filler and the key action is buried in a grammatically broken final sentence. This is under-specification rather than effective conciseness.

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 annotations, no output schema, and an empty input schema, the description needed to explain what a collection form is, how the agent should invoke or identify it, what response to expect, and how reprint differs from generate. None of that is present, so the tool cannot be invoked reliably.

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 has zero parameters and 100% schema coverage, so the description is not required to explain parameters. However, with additionalProperties set to true, the description could have clarified whether arbitrary inputs are expected in practice; still, the baseline for zero parameters is solid.

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 identifies a resource ('collection form') and an approximate action ('reprint'), but the opening 'Catalog entry' and the deployment note obscure rather than clarify purpose. It does not distinguish this operation from the sibling Shipping_generateCollectionForm or Shipping_getCollectionFormHistory, so an agent cannot tell whether this retrieves an existing form or creates a new one.

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?

The description provides no when-to-use guidance and names no alternatives. 'Runs in your Kuudo deployment, not here' is an operational context note, not a selection criterion, and there is no mention of when to prefer this over generateCollectionForm or when not to use it.

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