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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses that results include slug and project count, implying a read-only listing, but it does not cover pagination, completeness of results, auth/rate limits, or whether all collections are returned.

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 compact sentence with no wasted words, and the examples are useful. It is a noun-phrase fragment rather than a front-loaded verb statement, but it remains easy to scan.

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 list tool with a fully described optional locale, the description covers the resource and key returned fields. However, it leaves gaps around result completeness and why an agent would choose it over get_collection or search_repos.

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 single parameter, locale, is fully documented in the schema with its enum and default. The description adds no additional meaning about how locale affects summaries, so the baseline of 3 is appropriate given 100% schema 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?

The description identifies the resource (Repolode's topic collections), gives concrete examples such as AI agents and MCP servers, and states that each entry includes a slug and project count. It does not explicitly say 'list' or distinguish itself from get_collection, but the resource scope is clear.

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 gives no when-to-use guidance and does not mention alternatives. It never explains when to use list_collections instead of get_collection, search_repos, trending, or find_alternatives.

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