Get Top Rated Products

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only states that products are sorted by rating but does not explain behavior regarding the 'limit' parameter, default ordering, or handling of ties or empty results. Key behavioral traits are omitted.

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 extremely concise (one sentence), but it omits critical information such as the existence of the 'limit' parameter. While it earns its place for stating purpose, it sacrifices necessary detail, making it merely adequate.

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 tool's simplicity (one optional param, no output schema, no annotations), the description is incomplete. It does not mention the 'limit' parameter or default behavior, and among many sibling tools, it fails to provide sufficient context for correct selection and invocation.

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 input schema has one optional parameter 'limit' with constraints (0-100), but the description provides no explanation of this parameter. Since schema description coverage is 0%, the description must compensate but fails entirely to add meaning beyond the schema.

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 verb 'returns', the resource 'products', and the sorting criterion 'by rating (highest first)'. It effectively distinguishes this tool from siblings like 'getHighestRatedInCategory' which adds category context, and 'getMostReviewedProducts' which sorts by review count.

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 guidelines are provided about when to use this tool versus the 27 sibling tools. There is no mention of prerequisites, alternatives, or exclusions, leaving the agent without context for selection.

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