firestarter_review

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

Annotations already indicate readOnlyHint=false and destructiveHint=false. The description adds the prerequisite of 'delivered/completed order' and the uniqueness constraint, but does not disclose what happens on duplicate review attempts or any side effects of submission. This adds some context beyond annotations but not rich behavioral detail.

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 three concise sentences, each serving a purpose: stating the action, the use case, and the constraint. There is no redundant information, and it is front-loaded with the primary verb and resource.

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 submission tool with three parameters and no output schema, the description covers purpose, prerequisite, and constraint. It does not explain the response format or error behavior for duplicate reviews, but these are minor gaps given the tool's simplicity.

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 all three parameters (rating, comment, execution_id) are fully documented in the schema. The description merely reiterates the rating scale and comment, adding no extra semantics. The baseline of 3 applies.

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's function: 'Submit a review for a delivered/completed order.' It also specifies the rating scale (1-5 stars with optional comment) and the constraint of one review per order, which distinguishes it from sibling tools like firestarter_confirm_delivery or firestarter_return.

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 indicates when to use it: 'Use when the buyer wants to rate their purchase experience.' It also provides a key constraint ('Only one review per order is allowed'). It doesn't explicitly mention alternatives, but the context is clear and unambiguous.

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