gold_etsy_conversations_list

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

There are no annotations, so the description carries the behavioral burden. It discloses the read-only nature, unread-first ordering, preview-level content, the manual-sending boundary, and access prerequisites (BYOK, paid Pro-only). It does not describe response fields or pagination behavior, but it is largely transparent for a safe read-only tool.

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 compact and front-loaded, with the core read purpose first. The BYOK/paid clauses and 'pair with Claude' add useful context but also carry a slight promotional tone; still, the description is concise and not bloated.

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 one-parameter read-only tool, it covers access constraints and behavior well. However, without an output schema it does not explain the preview/return shape, and `limit` remains undocumented, so an agent is left to infer pagination and response fields.

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 0% and the description never mentions `limit` or how it affects results. The parameter name and default hint at pagination, but the description adds no meaning beyond the input schema; with low schema coverage it was expected to compensate and did not.

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 uses a specific verb and resource: 'Read your shop's buyer conversations.' It also adds ordering and scope ('unread-first previews'), and no sibling tool targets conversations, so it is clearly distinguishable from the other tools.

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?

It clearly states when to use the tool (to read buyer conversations) and explicitly sets an exclusion: 'Sending stays manual by design.' No sibling tool handles conversations, so the lack of a named alternative is not a significant gap.

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