Shipping_getRates

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

No annotations exist, so the description carries the behavioral disclosure burden. It does reveal that this is a catalog entry running in the Kuudo deployment rather than the current environment, which is useful. It does not mention authentication, side effects, or output shape, but 'Returns' implies a read-style operation.

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 concise at about 22 words. It front-loads the key facts, though 'Catalog entry' and 'Runs in your Kuudo deployment, not here' are somewhat redundant, which keeps it from being perfectly polished.

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 zero-parameter tool with no output schema, the description is mostly adequate: it explains where the tool runs and what it returns. It leaves some gaps, such as what an offering includes, whether arbitrary additional inputs are expected despite the empty schema, and what to do when not in the Kuudo deployment.

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 defined parameters, so there is no parameter documentation burden. The description does not add parameter-level detail, but with an empty schema this is not a meaningful gap; the baseline score of 4 applies.

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 says the tool 'Returns the available shipping service offerings,' which clearly names the verb and resource. The 'Catalog entry' phrase and deployment note add context without fully hiding the core purpose, but it does not explicitly differentiate from ShippingLegacy_getRates.

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 provides a meaningful context signal by stating that the tool 'Runs in your Kuudo deployment, not here,' which tells the agent where invocation is valid. However, it does not explicitly state when to use this tool over its siblings or give a direct when-not-to-use condition.

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