list_shipping_profiles

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds only the shape of the returned data ('destinations and costs'); it says nothing about pagination, ordering, whether all profiles are returned, or the cost currency/format. For a zero-parameter read tool this is acceptable but thin.

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?

A single short, front-loaded sentence fragment with no filler. Its only weakness is the missing verb, which makes it slightly less clear than a full sentence would be at no cost in length.

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?

The tool is trivial (no parameters), has no output schema, and its annotations cover the read-only nature, so completeness demands are low. The description conveys both scope ('Your' = shop-scoped) and the information returned, which is enough for an agent to call it correctly; only paging/return-volume details are absent.

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 is an empty object with zero parameters, so there is nothing for the description to disambiguate. Baseline 4 applies since the schema and description are consistent and no parameter meaning is missing.

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 fragment 'Your shipping profiles with destinations and costs' identifies the resource and hints at the payload (destinations, costs), but it never states a verb or that this is a listing operation — the agent must infer that from the tool name. It gives no explicit differentiation from siblings such as list_processing_profiles or list_listings.

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 call this tool, no preconditions, and no pointer to alternatives (e.g. a get-single-profile or create-profile sibling). The 'Your' possessive weakly implies shop-scoped retrieval, but nothing tells the agent when this is the right choice.

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