sephora_get_rewards

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does well by mentioning the authentication requirement, but it doesn't describe what happens if credentials are invalid, whether there are rate limits, what format the rewards information is returned in, or any error conditions. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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 perfectly concise with just two sentences that pack substantial information. The first sentence comprehensively lists all retrievable data, and the second sentence clearly states the authentication requirement. Every word earns its place with zero wasted text.

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 the tool's complexity (retrieving multiple types of rewards data), lack of annotations, and no output schema, the description does an adequate job but has clear gaps. It covers the purpose and authentication well, but doesn't describe the return format, error handling, or behavioral constraints that would be needed for the agent to use it effectively without trial and error.

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 the schema already documents both parameters (email and password) with clear descriptions about when they're required. The description adds marginal value by reinforcing the authentication context ('Requires Sephora account credentials if not already logged in'), but doesn't provide additional syntax, format, or usage details beyond what the schema already states.

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 specific action ('Retrieve') and resource ('Beauty Insider rewards information'), with detailed enumeration of what information is included (points balance, tier status, available rewards, recent activity, tier benefits). It distinguishes itself from sibling tools like sephora_add_to_basket or sephora_search_products by focusing exclusively on rewards data rather than shopping functionality.

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 about when credentials are needed ('Requires Sephora account credentials if not already logged in'), which helps the agent understand authentication prerequisites. However, it doesn't explicitly state when to use this tool versus alternatives or provide exclusion criteria, leaving some ambiguity about its specific use cases relative to other tools.

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