store_get_shipping_rates

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

Annotations already specify readOnlyHint, idempotentHint, and destructiveHint, covering the safety profile. However, the description adds no behavioral insight beyond what annotations provide—no mention of return data, error cases, or any operational nuance. It contributes nothing extra.

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 short (3 words) but fails to 'earn its place' because it simply repeats the tool name. It is not appropriately sized—it is under-specified and lacks any meaningful content. Prefrontal structure is absent.

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 get-by-ID operation, the description is incomplete. It doesn't explain what the response contains, that both shippingZoneId and shippingRateId are required (though schema shows this), or any error handling. There is no output schema, so the description should provide more context, but it doesn't.

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%, with each parameter (shippingRateId, shippingZoneId, altId, altType) documented. The description does not add any parameter context, so baseline 3 applies. Since it doesn't compensate for any gaps, no higher score is warranted.

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 'Get Shipping Rate' is essentially a restatement of the tool name 'store_get_shipping_rates'. It does not elaborate on the specific resource being fetched or differentiate from sibling tools like store_list_shipping_rates. It is nearly tautological, providing no additional clarity beyond what the name already conveys.

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 no guidance on when to use this tool versus alternatives. It does not mention that it fetches a single rate by ID, or contrast with listing rates, or any prerequisites. The agent is left without context on appropriate invocation scenarios.

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