etsy_get_favorites

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It correctly conveys a read-only operation via 'View' and notes the authentication requirement. It does not mention error behavior, defaults, or what happens with invalid usernames, but the essential safety profile is clear enough.

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 concise and front-loaded with the core purpose. The second sentence adds the important login prerequisite. Minor redundancy like 'on Etsy' is not harmful, but it does not carry much new information.

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 read-only tool with no required parameters and no output schema, the description is adequately complete: it states the resource, the action, and the key prerequisite. It does not enumerate optional filtering behavior, but that is already covered by the input schema.

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?

The input schema has 100% description coverage for its two parameters, so the baseline is 3. The description does not add meaningful semantic detail beyond what the schema already states, though the login requirement indirectly relates to the optional username defaulting to the logged-in user.

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 ('View') and the resource ('a user's favorited items and collections on Etsy'), which distinguishes it from siblings like etsy_add_to_favorites and etsy_get_item_details. The scope is specific and immediately understandable.

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 provides clear context for when to use the tool: to view a user's favorites and collections. It also discloses the login requirement as a prerequisite. However, it does not explicitly mention alternatives or when not to use it.

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