review_create

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

Without annotations, the description must disclose behavioral traits. It mentions the 'approved' parameter and its default to store's setting, which hints at moderation behavior. However, it does not state what happens after submission (e.g., visibility, notifications), whether duplicates are allowed, or any side effects.

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 front-loaded with a purpose statement but then repeats parameter names and descriptions in a list format, which is somewhat redundant given the schema. It could be more concise by focusing on unique behavioral details rather than paraphrasing schema fields.

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?

Even though an output schema exists, the description does not inform the agent about what the tool returns (e.g., created review ID, status, errors). This is critical for a creation tool, and its omission leaves the agent without a complete mental model.

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?

Despite 0% schema description coverage, the inline parameter list adds meaningful context: 'Star rating (1–5)', 'Short review title/summary', and 'Set approval status immediately'. This compensates well for the schema's sparse type-only meanings, though some parameters (e.g., 'content') lack additional semantics.

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') and the resource ('a product review'), making its core purpose unambiguous. It is distinct from the sibling 'review_list' tool, though it doesn't explicitly distinguish itself from other create tools.

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 no guidance on when to use this tool versus alternatives (e.g., when to use review_list or other creation tools). There are no prerequisites, when-not-to-use conditions, or context about intended use cases.

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