list_certificates

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

Annotations already mark the tool as read-only and idempotent, and the description adds genuinely useful behavioral details beyond that: it returns only one page, requires cursor-based pagination before reporting totals, and clarifies that expired certificates are included by default. It also discloses the required OAuth scope.

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 compact and well-structured: purpose first, then pagination behavior, then the critical default-filter warning, then the auth requirement. Every sentence adds practical value without padding.

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 endpoint with an output schema and eight optional filters, the description covers the most important behavioral traps: pagination, default status inclusion, and OAuth scope. It could be more complete by defining the date filter format or enumerating all filter semantics, but the output schema and self-explanatory parameter names reduce the gap.

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 0%, so the description must compensate. It does clarify the meaning of filter_status and its default, and explains the pagination semantics of page_cursor and has_more. However, it does not explain filter_domains, filter_course_id, filter_issued_gte/filter_issued_lte, or filter_student_id, leaving several parameters only self-documented by their names.

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 finds issued certificates with one row per certificate, which communicates a list operation on a specific resource. It does not explicitly contrast itself with the sibling get_certificate tool, so it stops short of full sibling differentiation.

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 useful usage context: results are paginated, you must check has_more and use next_cursor, and filter_status defaults to all so expired certificates are included unless narrowed. It does not explicitly say when to use this tool instead of get_certificate, but the pagination and filtering guidance is strong.

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