etsy_listing_materials_add

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

With no annotations, the description carries the full burden. It discloses that the tool adds and merges, but does not mention authorization needs, rate limits, side effects, or error conditions. The behavioral traits are minimal but not misleading.

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 very concise (one sentence, 10 words) and front-loaded with the action. Every word is informative. It could benefit from a bit more detail, but it is not verbose.

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 3-parameter tool with no output schema, the description is adequate but incomplete. It does not describe return behavior, idempotency, or success/failure signals. Given low complexity, a score of 3 is appropriate.

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 low (33%). Only 'new_materials' has a schema description. The tool description does not provide additional meaning for 'shop_id' or 'listing_id', and adds only the merge context for 'new_materials'. Given the low coverage, the description should compensate but fails to do so.

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?

Description clearly states 'Add materials to a listing (merges with existing)'. The verb 'Add' and resource 'listing materials' are specific. The parenthetical 'merges with existing' distinguishes this from a replace operation, which is relevant given the sibling tool 'etsy_listing_materials_update'.

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 implies usage for adding materials without replacing existing ones, but it does not explicitly state when to use this tool versus 'etsy_listing_materials_update' or other siblings. No when-not or alternative guidance is provided.

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