products_add_follower

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

No annotations provided, so the description carries the full burden. It discloses that adding a follower results in notifications for product updates (details, deals, price changes, etc.) and the access requirement. This is comprehensive for a simple creation 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 5 sentences, well-structured: action, definition, notification details, note. It's concise but could trim redundant phrases like 'This is useful for...' while keeping essential context.

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 tool with 2 parameters and no output schema, the description is fairly complete. It explains the effect and a key precondition. However, it omits potential edge cases (e.g., what happens if user already follows, error handling for access denial).

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 100%, so baseline is 3. The description adds value by explaining the purpose of the parameters (product ID and user ID) in the context of follower management, enhancing understanding beyond the schema's simple descriptions.

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 'Add a follower to a product' and explains the purpose of followers (notifications, collaboration). It distinguishes from sibling tools like deals_add_follower by specifying 'product' in both name and description.

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 explains when to use the tool (adding followers for notifications) and includes a prerequisite condition: 'Users can only be added as followers if they have access to the product.' While it doesn't explicitly mention when not to use, the context of followers for products is well-established.

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