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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the write/safety profile is covered structurally. The description adds nothing beyond that: no permission requirements, no idempotency or duplicate-handling behavior, no statement of whether a provider must be registered, and no indication of what the call returns.

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 sentence that front-loads the verb and resource and omits filler. It is efficient, though it wastes its brevity on restating parameter names instead of conveying routing or behavioral information.

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 mutation tool with nested objects, one required field, and no output schema, the definition is minimally adequate. It does not say what a successful creation yields (e.g., a shipment ID) or how it relates to the quote tool, which an agent would need for correct sequencing.

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 includes nested object descriptions, so the schema already carries parameter meaning. The description merely echoes the field list (origin, destination, package, provider) without adding format, constraint, or default details. 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?

Specific verb (Create) plus resource (equipment shipment) with an enumeration of the payload fields, which lets an agent distinguish it from read-side siblings like get_shipments and get_shipment_quote. It stops short of explicitly contrasting itself with those siblings.

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 guidance on when to use this versus alternatives. Notably, get_shipment_quote and get_logistics_overview exist nearby, and the description never says whether a quote must be obtained first or when a shipment should be created directly. No prerequisites or preconditions are stated.

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