market_favorites

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

No annotations are provided, so the description must carry the full burden. It discloses the actions (list, add, remove) but does not explain side effects, authentication needs, or error behavior. The behavioral transparency is minimal.

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 with clear front-loading. It is concise and to the point, though it could be slightly expanded for completeness without losing brevity.

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 no output schema, no annotations, and low parameter coverage, the description is insufficient. It lacks information on return values, pagination, error handling, and how this tool fits into the broader workflow among 32 sibling tools.

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 25% (only 'action' has a description). The description adds 'Omit action for list' but does not explain the roles of product_id, name, or store, leaving their semantics unclear for add/remove operations.

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 states 'Manage favorite products: list, add, or remove,' clearly specifying the verb and resource. While it distinguishes from siblings by focusing on favorites, it could better contrast with similar tools like market_cart or market_substitutes.

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 guideline 'Omit action for list' provides a specific usage hint, but it lacks guidance on when to use this tool versus alternatives (e.g., market_cart for cart management) and does not mention prerequisites or exclusions.

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