calculate_shipping

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

No annotations are provided. The description mentions a POST request but does not disclose whether the operation has side effects (e.g., creating a rate quote) or is purely read-only. It also omits what the response contains, leaving the agent guessing about behavioral traits.

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 relatively concise but mixes purpose, endpoint, and parameter lists in one sentence. It could be better structured with bullet points for readability. Every word is functional but not highly efficient.

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?

With 15 parameters, no output schema, and no annotations, the description fails to provide context on what the tool returns or how to interpret results. The agent lacks information about the output format or possible errors, making it incomplete.

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 description coverage is 100%, so the schema already documents each parameter. The description summarizes required vs optional parameters but does not add new meaning beyond the schema. Baseline score of 3 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 'Calculate shipping rates.' with a specific verb and resource. It distinguishes from siblings like 'list_shipping_services' which lists services, not rates. The endpoint POST /shipping/calculate further clarifies the action.

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 lists required and optional parameters, indicating what inputs are needed. However, it does not explicitly state when to use this tool over others or provide context on prerequisites (e.g., need to have shipping services set up). No explicit usage guidance.

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