list_category

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

No annotations provided, so description carries full burden. It describes behavior: returns ranked list with specific fields, sorting by rating or price, filtering free_only. It does not mention pagination or rate limits, but those are not critical for this tool.

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?

Well-structured with sections (BEHAVIOR, USAGE GUIDELINES, EXAMPLE QUERIES). Front-loaded with main purpose. Every sentence adds value; no redundancy.

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?

Despite no output schema, the description fully explains what each entry includes (name, rating, free plan, price, link). Covers all aspects needed: sorting, filtering, example queries, and sibling tool combinations.

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?

Schema coverage is 100%, and description adds additional context: explains sort_by options ('rating' vs 'startingPrice') and free_only filter. It also provides the category slug hint referencing list_categories.

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 lists all verified SaaS tools in a specific category with pricing, ratings, and free plan status. It distinguishes from siblings like get_leaderboard (top 10 only) and list_categories (list categories).

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?

Provides explicit usage examples and when to use vs alternatives: 'Use list_categories first if you are unsure of the correct category slug' and 'Combine with get_leaderboard when the user wants only the top-rated tools'.

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