he_get_ratings

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

No annotations are provided, so the description carries full burden. It describes a read operation but does not disclose any behavioral traits beyond the obvious. It lacks information on authentication requirements, rate limits, error handling (e.g., if homeId is invalid), or pagination of multiple reviews.

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 of 16 words, front-loaded with the action ('Get reviews and ratings') and key details. No redundant information. However, it could benefit from additional context without becoming verbose.

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 one-parameter tool with no output schema, the description is minimal. It does not explain the return format (e.g., whether it returns a single rating or multiple, structure of feedback text). Lacks information on expected output, which may cause confusion for an AI agent.

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% (one parameter 'homeId' described as 'HomeExchange property ID'). The description adds context that the tool is for a property, but does not add new meaning beyond the schema. Baseline score of 3 is appropriate since the schema already provides sufficient parameter documentation.

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 tool retrieves reviews and ratings for a HomeExchange property, listing specific aspects (cleanliness, expectations, communication scores, feedback text). It explicitly distinguishes from siblings like 'he_get_home' which gets property details, and 'he_get_user_ratings' which gets user ratings.

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 versus alternatives, or any prerequisites or conditions. For example, it doesn't mention that the property must exist or that it reads data without side effects. Sibling tools exist for related data, but no explicit when-to-use or when-not-to-use is given.

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