send_shipping_info

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

With no annotations, the description partially carries the burden. It discloses the automatic platform detection behavior, but does not mention potential side effects (e.g., quota usage, permission requirements, failure modes). The description adds some transparency but could be more comprehensive.

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 sentences: the first establishes the core function, the second adds critical behavioral detail. Every word contributes, and the structure is front-loaded with the key verb and resource.

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 existence of an output schema and full parameter descriptions in the schema, the description is mostly complete. It explains the automatic routing behavior. However, it lacks mentions of prerequisites (e.g., connected social accounts) or limitations (unsupported platforms), which would enhance completeness.

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?

Input schema coverage is 100%, so the baseline is 3. The description does not add any additional meaning beyond the schema's parameter descriptions; it merely restates the tool's purpose. No extra value for parameter understanding.

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 clearly states the action (send) and the resource (shipping/tracking information to a customer). It adds distinctive context by specifying the automatic platform detection (Instagram DM, WhatsApp), which differentiates it from generic messaging tools like reply_to_message.

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 implies usage when shipping information is ready to be sent, but it does not explicitly state when to use this tool over alternatives (e.g., if you need to send a custom message, use reply_to_message). No when-not guidance is provided.

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