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

The description adds useful behavioral detail beyond the annotations: results are sorted by vote count, and votes are limited to one per signed-in member per bot. The readOnly, idempotent, and non-destructive annotations are consistent with a simple read/list operation.

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 concise at two sentences and front-loads the core behavior. The first sentence has a minor grammar issue ('Listings the community voted up'), but no redundant filler or schema repetition exists.

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 read-only list endpoint with one optional parameter, the description covers the main idea and ordering well. However, the complete lack of guidance on the 'limit' parameter leaves a notable gap, even though an agent can safely call the tool without providing it.

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?

There is one parameter, 'limit', with 0% schema description coverage. The description never mentions 'limit', its default, its effect on the result count, or how it interacts with the ordering. Since schema coverage is low, the description was responsible for explaining this parameter and did not.

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 identifies a specific resource ('listings the community voted up') and a clear ordering ('most votes first'). It is understandable even if grammatically awkward, and it clearly differs from siblings like 'latest' and 'search_bots' by emphasizing community voting and vote-based ranking.

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 context is implied: use this tool when you need community-voted listings in vote order. However, it does not explicitly tell an agent when not to use it or mention alternatives such as 'latest' or 'search_bots'.

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