list_shipping_services

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

No annotations are provided, so the description must fully disclose behavior. It only states it returns available shipping services, but omits details like response structure, pagination, or error conditions. This leaves the agent with limited understanding of the tool's output.

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 extremely concise (two sentences, 15 words) and front-loads the purpose. Every word serves a clear function: stating action, endpoint, and return type. No unnecessary information.

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 simple listing tool with no parameters and no output schema, the description is minimally complete. However, it could elaborate on the type of objects returned (e.g., service names, IDs) to improve agent understanding. The absence of any behavioral detail beyond 'returns available shipping services' is a gap.

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 parameters, so no param documentation is needed. The description naturally adds no parameter semantics, but the baseline for zero parameters is 4, as the schema already fully covers the input.

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 explicitly states the tool lists shipping services, specifies the endpoint 'GET /shipping/services', and distinguishes it from the sibling tool 'calculate_shipping' which computes costs. This provides a clear and unique purpose.

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 does not provide any guidance on when to use this tool versus alternatives (e.g., 'calculate_shipping'). It lacks context on prerequisites or typical flow. However, the purpose is self-evident for a listing tool.

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