chitchats_get_shipment

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

The readOnlyHint annotation already signals a safe read operation, and the description adds useful context by naming the exact categories of returned data (cost breakdown, tracking info, recipient details). For a simple retrieval tool, this is sufficient behavioral disclosure; no contradictions exist.

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 a single, front-loaded sentence that immediately states the action and resource, then lists valuable details. Every word earns its place with no filler or redundancy.

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 one-parameter read-only retrieval tool with no output schema, the description is complete: it names the identifying input, clarifies the scope ('a specific shipment'), and previews the return content. The readOnlyHint covers safety expectations, and no further output explanation is required.

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 input schema already provides 100% coverage for the single parameter ('id': 'Shipment ID'). The description reinforces the role of the ID by saying 'specific shipment by ID' but does not add meaningful new semantic detail beyond what the schema provides.

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 uses a specific verb+resource structure: 'Get full details of a specific shipment by ID' and enumerates the included content (cost breakdown, tracking info, recipient details). This clearly distinguishes it from sibling tools like chitchats_list_shipments (list all) and chitchats_track_shipment (tracking-only).

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 clearly implies when to use this tool: when you have a specific shipment ID and need full shipment details. It does not explicitly mention alternatives or exclusions, but the 'specific... by ID' phrasing provides clear context relative to sibling list/track tools.

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