Shipping_getTracking

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It implies a read-only operation by saying 'Returns,' but it does not disclose authorization requirements, input needs, return format, or error behavior. 'Runs in your Kuundo deployment, not here' is a vague deployment note rather than a clear behavioral trait.

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 short, using three brief sentences without excess detail. The first sentence, 'Catalog entry,' is somewhat vague and the main action is delayed, but the overall length is well controlled.

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?

There is no output schema and no annotations, yet the description only promises generic 'tracking information.' It does not specify what shipment identifier is required, what tracking fields will be returned, or how this tool differs from sibling ShippingLegacy_getTrackingInformation. This is too thin for a tool with no structured schema to fall back on.

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 has zero declared properties, so there are no parameter semantics for the description to enrich. The schema also sets additionalProperties to true, which is unusual, but with 0 parameters the baseline of 4 is appropriate.

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 and resource: it 'Returns tracking information for a purchased shipment.' This makes the core purpose clear. However, it does not differentiate itself from the closely related sibling ShippingLegacy_getTrackingInformation, which also appears to return tracking-related data.

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?

There is no guidance on when to use this tool versus ShippingLegacy_getTrackingInformation or any other shipping tool. The phrase 'Runs in your Kuundo deployment, not here' provides an environment caveat but does not help an agent decide between alternatives.

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