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

Annotations already cover the read-only, non-destructive, open-world profile, and the description adds genuinely new context: results are ordered newest-first, each review may include your own response, and a Cotlet API key with app access is required. It stops short of describing pagination or result limits.

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 field list 'rating, text, date and your response' is stated twice in nearly identical wording, which wastes space in an otherwise short description. The core purpose is front-loaded, but the redundancy costs it.

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 read-only list tool with full schema coverage and safety annotations, the description covers the return fields, ordering, and auth requirement adequately. It leaves only minor gaps (pagination, volume limits) for what is a straightforward listing operation.

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 description coverage is 100%, so the schema already documents all four parameters. The description only restates the rating and unresponded_only filters, adding a small semantic hint ('to find what still needs an answer') but no syntax or format detail beyond the schema.

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?

States a specific verb (lists) and resource (reviews of one course), and enumerates the returned fields (rating, text, date, your response). It is clearly distinguishable from siblings like udemy_respond_to_review or udemy_list_questions.

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?

Offers implied usage via 'Filter by star rating or unresponded_only to find what still needs an answer', but never states when to prefer this tool over alternatives or any prerequisites beyond the auth note. Context is suggested rather than spelled out.

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