Collect a premium delivery

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

With no annotations, the description carries the full burden of behavioral disclosure. It discloses that delivery is separate from the order and requires a fulfilled status, which is useful. However, it does not explicitly state that this is a read-only operation, nor does it mention error conditions (e.g., what happens if status is not fulfilled). This is a moderate gap for a get 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 two concise sentences with the core purpose front-loaded. It conveys the main function and the key usage condition without any filler. Every sentence earns its place.

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 tool with a single parameter and no output schema, the description covers the essential context: what it returns, when to call it, and how it differs from inline delivery. It does not specify the response format or error behavior, but given the low complexity, this is a minor omission.

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 0%, so the description must compensate. It only implies that orderId refers to the fulfilled premium order but does not explicitly state that orderId is the premium order's ID or how to obtain it. The description adds minimal meaning beyond the schema's bare property definition.

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 ('collect') and resource ('premium delivery') and clarifies that it returns credentials/invite/link. It distinguishes from store orders by noting delivery is not inline. However, it does not name a specific sibling tool like get_premium_order, relying on a category contrast rather than explicit differentiation.

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 gives a clear condition for use: 'you must call this once status is fulfilled.' It contrasts with store orders, implying when not to use it (for store orders). It lacks explicit mention of alternatives, but the context is sufficient for an agent to infer it is the dedicated delivery retrieval tool.

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