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

No annotations are provided, so the description carries full responsibility for disclosing behavioral traits. It does not mention whether authentication is required, any rate limits, pagination behavior, or the structure of the returned data. While 'get' implies a read operation, the description does not explicitly confirm read-only status or add context that would help an agent understand side effects or edge cases.

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, front-loaded sentence with no filler or redundancy. Every word earns its place, making it highly concise and efficiently structured.

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 low complexity (one optional parameter, no output schema, no annotations), the description is reasonably complete. It clearly states the tool's purpose and key sorting behavior. However, it could be slightly more helpful by mentioning that it returns a list of listings (even though that's implied) or by clarifying that sorting is by average rating in descending order. This minor gap prevents a perfect score.

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 provides 100% coverage for the sole 'limit' parameter, including its default, minimum, maximum, and a clear description. The tool description adds no additional parameter semantics, but since the schema already does the heavy lifting, a baseline score of 3 is appropriate.

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 'Get top-rated marketplace listings sorted by average rating' uses a specific verb ('Get') and identifies the resource ('marketplace listings') with a clear qualifier ('top-rated', 'sorted by average rating'). This naturally distinguishes it from sibling tools like browse_marketplace and get_featured, despite not explicitly naming alternatives.

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 only what the tool does, with no guidance on when to use it versus alternatives. There is no mention of exclusions, prerequisites, or sibling tools that might be better suited for other needs. The implied usage ('use when you want top-rated listings') is minimal and does not help an agent make a nuanced tool selection decision.

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