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

Read-only, non-destructive annotations cover the safety profile, and the description adds genuine context beyond them: the inclusion criteria, pagination at 100 per page, and the output date encoding (YYYYMMDD). With no output schema, it does the work of describing the return shape reasonably well, though it omits sort order and empty-result 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?

Four dense sentences, front-loaded with the payload contents before the filtering and constraints. The trailing 'GET /reports/courses/{course_id}/' is marginally useful for API mapping; the '100 per page' detail duplicates the page parameter description but is cheap.

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 13-parameter, no-output-schema report, the description covers what is returned, the inclusion rule, and pagination – enough for correct invocation. Remaining gaps (range-pair semantics, count_only interplay, sort order) are minor and partly covered by the schema.

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?

Coverage is 54%; the description lumps status, progress, score and date filters together without explaining that score/progress/date are min/max range pairs or giving the status enum semantics. The heavy lifting (user_filter grammar, page, count_only) is already in the schema, so a baseline 3 is appropriate.

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 clearly that this is a per-user report for a single course, enumerating the returned fields (user, status, progress %, score, start/completion date) and the endpoint. That distinguishes it in substance from list_course_users (roster) and user_report (cross-course), though no sibling is named explicitly.

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 inclusion rule ('limited to users currently enrolled who accessed the course or have score data') hints at when this report is appropriate, but there is no explicit when-to-use / when-not / alternative routing against user_report or certification_report. Usage is implied rather than stated.

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