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

Annotations provide readOnlyHint=true, but the description adds meaningful context: it specifies the alerts are 'active' and requires their account, which informs authorization expectations. It doesn't contradict annotations and adds value beyond them.

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 short sentences, front-loaded with action, no fluff. Perfectly concise.

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 zero-parameter list tool with a readOnly annotation)Skip it: No output schema, but the description gives the essential context (active alerts, account requirement). It's complete enough for an agent to know what to expect, though it doesn't describe format.

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?

There are no parameters, so the schema fully covers parameter semantics. The description inherently covers the only 'input' (the user's identity) by stating it requires their account. Baseline 4 is appropriate due to zero parameters.

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 tool lists the user's active price alerts on PriceTrack, distinguishing it from siblings like create_price_alert and get_price_history. The verb 'list' and resource 'price alerts' are specific and unambiguous.

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?

It notes that the alerts are the user's own and requires their account, giving clear context for when to use. It doesn't explicitly contrast with other list-type tools, but the context is sufficient given the simple scope.

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