etsy_user_favorite_shop_add

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

No annotations available; description does not disclose behavioral traits such as idempotency, permissions, side effects (e.g., duplicate handling), 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 a single sentence, concise but overly minimal. It earns its place but fails to provide necessary detail.

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 no output schema, no parameter descriptions, and no annotations, the description is severely incomplete for a write operation. It lacks critical context like idempotency or error behavior.

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 coverage is 0%; description does not explain what user_id and shop_id represent or any constraints. The schema defines them as integer or string but the description adds no meaning.

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 the action ('Add') and the resource ('a shop to a user's favorites'), distinguishing it from sibling tools like etsy_user_favorite_listing_add (adds a listing) and etsy_user_favorite_shop_remove (removes a shop).

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 vs alternatives (e.g., when to add vs remove). No prerequisites or context provided for use.

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