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

No annotations are provided. The description does not disclose whether this is a read-only operation (though implied by 'get'), any authentication needs, rate limits, or pagination behavior beyond the limit parameter. The behavioral context is minimal and relies on inference.

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 a single sentence that efficiently conveys the tool's purpose and output. No extraneous words or repetition. It is front-loaded with the 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?

Given no annotations, no output schema, and only one parameter, the description is borderline adequate. It explains what the tool does and what it returns, but it lacks detail on ordering, filtering (e.g., by date or rating), and any usage caveats. It meets the minimum for a simple read tool but leaves room for improvement.

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?

The schema has 100% description coverage for its single parameter (limit). The description adds value by listing the output fields (reviewer name, rating, title, content), which are not in the input schema. This helps the agent understand what data will be returned, going beyond the schema alone.

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 ('Get') and resource ('published reviews for this site (Wix Reviews)'). It also specifies the return fields (reviewer name, rating, title, content), distinguishing it from sibling tools that deal with other entities like bookings, events, or products.

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?

No guidance is provided on when to use this tool vs. alternatives (e.g., list_products, list_blog_posts). There is no mention of prerequisites, filtering options, or when not to use this tool. The description is purely functional.

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