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

Beyond the annotations, the description discloses the OAuth requirement, the required 'alerts' scope, and that anonymous callers are prompted to authorize. It also states the specific alert fields returned, providing behavioral context over and above the readOnlyHint and idempotentHint annotations. No contradiction with annotations.

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?

Two tight sentences: the first states what the tool returns, and the second states when to use it and the authentication requirement. Every sentence earns its place, and the core purpose is front-loaded.

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 parameterless, read-only, idempotent tool with rich annotations, the description covers the function, exact result fields, usage context, and auth behavior. The absence of an output schema is compensated by naming the precise fields returned. Nothing critical is missing.

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 tool takes zero parameters, so there is nothing to document in the input schema. The description appropriately focuses on the return data and usage context rather than inputs, matching the baseline of 4 for parameterless tools.

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 a specific verb ('Returns') and resource ('the signed-in user's cashback and gift card alerts'), and enumerates the fields returned (store, type, threshold percent, last notification). This clearly distinguishes it from sibling tools such as get_my_profile or get_my_favorite_stores by the alert-specific resource and the enumerated return data.

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 explicitly names two use cases: answering 'what alerts do I have?' and being used before changing an alert. This implies it is the read/precondition tool for the mutation siblings set_store_alert and remove_store_alert, but it does not name those alternatives or explicitly state when not to use it. The context is still clear enough for an agent to route correctly.

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