etsy_shop_shipping_profiles_list

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

The annotation readOnlyHint=true already signals a read operation. However, the description adds no further behavioral traits, such as whether pagination is supported, response structure, or any limitations. Beyond the annotation, transparency is minimal.

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 one sentence (7 words) with no wasted words. It is front-loaded and efficient, but it could include slightly more detail (e.g., parameter clarification) without losing conciseness.

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?

Given the tool's simplicity (1 param, no output schema), the description is incomplete. It lacks information on the return value (e.g., list of profile objects), whether the list is full or paginated, and how this tool fits into the workflow among related shipping tools.

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 tool description does not explain the meaning or format of the required shop_id parameter. With 0% schema description coverage, the agent receives no guidance on what this parameter represents, leaving it to infer from the parameter name alone.

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 'List all shipping profiles for a shop' clearly states the verb (list) and resource (shipping profiles) with a scope (for a shop). It distinguishes from sibling tools like etsy_shop_shipping_profile_get (singular) and other list tools by specifying 'shipping profiles'.

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?

No usage guidelines are provided. The description does not indicate when to use this tool versus alternatives such as etsy_shop_shipping_profile_get for a single profile or etsy_shipping_profile_destinations_list for listing destinations. No when-not-to-use or prerequisites are mentioned.

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