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

Beyond the annotations (readOnlyHint=false, destructiveHint=false), the description discloses that rating the same thing again replaces the earlier rating, which is a behavioral trait an agent must know. It also implies the rating is non-trivial and valuable, adding context. No contradictions 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?

Four sentences with no redundancy. The core purpose is front-loaded, and each subsequent sentence adds a distinct supporting detail (replacement, honest feedback). Nothing extraneous.

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 rating tool with a clear schema, the description fully covers what to rate, when, how (1-5 with note), and the replacement behavior. No output schema is needed; the description is sufficient for an agent to call it correctly.

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 coverage is 100%, and the schema already explains what each parameter is (product_id, rating, note). The description adds nuance about the rating scale ('Rate 1 to 5', '1 means do not buy this again' is in schema) and the note ('say why in a sentence'), but these mostly reinforce schema details rather than add new meaning. The description provides rationale (real use value) but not essential parameter guidance.

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 verb 'Record'/'Rate' and the resource 'something you bought', with the specific condition of 'after you have actually used it'. This distinguishes it from generic reviews or pre-purchase ratings, making the purpose 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?

The description provides strong usage context: it's for items you paid for and used for real work, and it contrasts with 'any review page'. It also explains the replacement behavior. However, it does not explicitly name alternative tools (like submit_feedback) or state when not to use it, so it falls short of a 5.

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