etsy_shipping_profile_upgrade_create

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

No annotations are provided, so the description bears full burden. It indicates a write operation ('Create') but omits critical behavioral details such as authorization requirements, idempotency, side effects (e.g., overwriting existing upgrades), or error conditions.

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 brief (one sentence) but fails to convey essential information. While it avoids verbosity, it is under-specified and does not earn its place by providing enough context to be useful.

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 10 parameters (6 required), no output schema, and low schema coverage, the description must compensate but provides no context about return values, required preconditions, or the creation process. The tool is highly incomplete for an agent to use effectively.

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 only 20%, and the tool description adds no parameter details. Many parameters (shop_id, mail_class, delivery days, etc.) lack any semantic explanation in both schema and description, leaving the agent without meaningful guidance.

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 clearly states 'Create a shipping upgrade for a profile', specifying the action and resource. It distinguishes from sibling tools like delete, update, and list, but lacks mention of the scope (shop/profile).

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 guidance on when to use this tool versus alternatives (e.g., update, delete). No context about prerequisites or exclusions. The description is a single sentence without any usage direction.

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