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

With no annotations, the description carries the full burden: it does disclose the key behavioral rules, one review per order and the paid/delivered eligibility gate. It omits auth/ownership requirements, what happens when the gate fails, and whether the review can be edited or deleted afterward.

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?

A single dense sentence with the eligibility constraint front-loaded and no filler. It is arguably terse given the 0% schema coverage, but every clause earns its place.

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 three-parameter mutation with no annotations and no schema descriptions, the description covers eligibility and the one-review limit but leaves parameter semantics and failure behavior unexplained. Adequate to attempt the call, not complete for a mutation tool.

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 0% for all three parameters. The description restates the rating bounds already encoded in the schema (minimum 1, maximum 5) and hints at order_id through 'verified paid order', but says nothing about the optional 'review' field, its expected length, or order_id format.

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 gives a specific verb+resource ('Leave ... review') and adds the 1-5 star scope plus the eligibility constraint, which clearly separates it from read-side siblings like get_product_reviews. It does not explicitly name a sibling, but the write-vs-read split is obvious from the phrasing.

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 states when the tool is usable — only for a verified paid order — and carves out the timing rule for service orders ('reviewable after delivery'). That is real when/when-not guidance, though it never points to an alternative tool for ineligible cases.

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