get_reviews

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

No annotations provided; description does not indicate read-only nature, authorization needs, or side effects. As a 'get' operation, it's likely non-destructive, but the description should clarify this given lack of 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?

Description is brief and includes a structured args list, but it redundantly restates schema defaults (sort, limit). The verb 'Get' could be more precise.

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?

Covers basic usage with parameters, but lacks details on response format, error handling, or rate limits. Output schema exists but is not referenced.

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?

Description provides clear meaning beyond schema: specifies allowed values for 'sort' (newest, highest, lowest, helpful) and range for 'limit' (1-100, default 20). This compensates fully for the 0% schema description coverage.

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?

Description states 'Get reviews for a business' with a specific verb and resource, clearly distinguishing from siblings like 'get_business' which retrieves business details. However, it doesn't explicitly differentiate from other review-related siblings if any existed.

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 explicit guidance on when to use this tool versus alternatives like 'get_business' or 'search'. The purpose is implied but not contrasted with siblings.

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