firestarter_review

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

Annotations already indicate this is a write operation (readOnlyHint=false) and not destructive (destructiveHint=false). The description adds useful context: the requirement that the order must be delivered/completed, and the one-review-per-order restriction, which goes beyond the 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?

The description is three short sentences, front-loaded with the core purpose, and every sentence adds value. No redundancy or filler.

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 tool with three parameters and no output schema, the description covers the use case, preconditions, and a key constraint. It doesn't mention error conditions, but that's acceptable given the simplicity and the clarity of the description.

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%, so all parameters are fully documented. The description mentions the rating scale and optional comment, but these details are already present in the schema. It does not introduce any new meaning beyond what the schema provides.

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 action (submit a review) and the specific resource (a delivered/completed order). It also specifies the rating scale and the fact that it's for buyers, distinguishing it from sibling tools like firestarter_confirm_delivery or firestarter_track_order.

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?

Explicitly says "Use when the buyer wants to rate their purchase experience" and adds a key constraint: "Only one review per order is allowed." It doesn't explicitly mention alternatives, but the condition is clear enough for an agent to decide when to invoke this tool versus other order-related actions.

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