etsy_shops_by_owner

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

Annotations already indicate readOnlyHint=true, so the description's claim of 'get' aligns. However, it adds no extra behavioral context (e.g., pagination, rate limits, or auth requirements) beyond what annotations provide.

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 efficient sentence, front-loaded with the core purpose. However, it is too brief and omits helpful details, making it under-specified for completeness.

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 three parameters (including pagination), no output schema, and only a bare description, the tool definition lacks context about default limits, pagination behavior, or response size. It is incomplete for effective use.

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 33% (only user_id described). The tool description does not explain limit/offset parameters or their roles, leaving the agent to rely on schema alone. This is insufficient given low schema coverage.

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 (get) and resource (shops owned by a specific user). It distinguishes itself from siblings like etsy_shop_get (single shop by ID) and etsy_shop_find (search shops by criteria) by focusing on ownership.

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 via ownership context but offers no explicit when-to-use or when-not-to-use guidance. It does not mention alternatives like etsy_shop_get or etsy_shop_find, leaving the agent to infer.

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