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

The annotations already disclose that the tool is read-only, idempotent, open-world, and non-destructive. The description adds useful context by saying the tool has a fixed endpoint and expects the exact request payload in the body, but it does not cover auth needs, rate limits, or other behavioral constraints beyond the annotations.

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 definition is front-loaded with a specific endpoint and operation, but it repeats 'get shipment details operation' several times and includes boilerplate such as 'Search terms' that is not essential for invocation. The structure is serviceable but not tight.

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 single-body-parameter tool with an output schema and rich annotations, the description is largely sufficient: it names the request type, the main field, and the need to send the payload exactly. It could be stronger if it fully described the expected body object or any authentication constraints.

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 coverage is high, but the body schema only describes the parameter generically. The description adds meaningful request semantics by identifying the request type as GetShipmentDetailsRequest and calling out TrackingCode: string as a main field, which helps an agent construct the body.

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 names a specific verb and resource: POST api/Dispatch/GetShipmentDetails and the 'get shipment details' operation in shipping/dispatch. It also distinguishes the tool from a generic endpoint caller, but it does not explicitly contrast it with nearby siblings such as hgr_post_dispatch_updateshipmentdetails or hgr_get_dispatch_get.

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 'Use when' clause is circular: it says to use the tool when a client needs to run the get shipment details operation, without explaining when to choose it over alternatives. There is no guidance about when not to use it or which sibling tool handles related dispatch lookups.

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