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

No annotations are provided, so the description bears full burden. It discloses the return format but omits important behavioral traits such as read-only nature, required permissions, or any rate limits. For a tool that presumably reads data, this is a notable gap.

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 two sentences, direct and void of unnecessary information. Every word adds value, making it easy to parse quickly.

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 the simple structure (one parameter, no output schema), the description sufficiently covers what the tool returns. However, the lack of output schema means the description must compensate, and it does by listing return fields. Minor gap: no mention of ordering or default behavior beyond the schema's 'default 10'.

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?

With 100% schema description coverage and a single parameter ('limit'), the description adds no extra meaning beyond the schema. The baseline score of 3 is appropriate as the schema already documents the parameter's purpose and constraints.

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 specifies the action ('Get') and the resource ('published reviews') and explicitly lists the returned fields (reviewer name, rating, title, content). This distinguishes it from sibling tools like list_products or get_site_info.

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 states it returns reviews 'for this site' but does not provide guidance on when to use this tool versus alternatives (e.g., list_blog_posts for content not reviews). No exclusions or prerequisites are mentioned.

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