get_top_rated

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

No annotations are provided, so the description must convey behavioral traits. It discloses the sorting behavior and optional filters, but does not detail return format, pagination, or other limitations. The open-ended nature of 'top-rated' leaves some uncertainty about the output structure, though the schema partially compensates for parameter-related behavior.

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 exceptionally concise: two short sentences, front-loaded with the core action and resource. The sorting information and filter options are presented efficiently without any redundant wording.

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 listing tool with no output schema, the description covers the essential context: source, sorting, and filters. It does not explicitly state the return shape, but the tool's simplicity and the schema's parameter documentation make this a minor omission, leaving it sufficiently complete for typical use.

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 comprehensive descriptions for all three parameters, including enums and limits, so the baseline is 3. The description only restates that filtering is optional, adding no new semantic value beyond what the schema already offers.

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's function with a specific verb ('Get'), identifies the resource ('top-rated AI agent tools from SkillsIndex'), and specifies the sorting by overall score (0-100). It also mentions optional filters, which further distinguishes it from sibling tools like search_tools or get_tool.

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 provides clear context for when to use this tool: to retrieve top-rated tools sorted by score, with optional ecosystem or category filtering. It does not explicitly mention alternatives or exclusions, but the purpose is unambiguous enough to guide the agent's choice.

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