certificates_get_collection

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

No annotations are provided, so the description carries the full disclosure burden, yet it says nothing about authentication, pagination behavior (implied by limit/sort), rate limits, or what the returned collection contains. The REST path conveys only that a GET happens.

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?

It is short, but the parenthetical duplicate of the same path adds no information and the single sentence does not earn its place. Brevity here reflects under-specification rather than efficient communication.

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 9-parameter, filterable collection endpoint with no annotations and no output schema, the description provides nothing an agent needs to call it correctly or interpret results. It is completely inadequate for the tool's complexity.

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% across all 9 parameters (sort, limit, include, filters, fields), each with its own description and enums. The description adds nothing beyond the schema, so the baseline of 3 applies.

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 is literally the HTTP verb plus path repeated twice ('GET /v1/certificates (GET /v1/certificates)'). It restates the tool name rather than describing what listing certificates accomplishes, and it does nothing to distinguish this root collection from siblings like certificates_get_instance or pass_type_ids_certificates_get_to_many_related.

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?

No guidance whatsoever on when to use this collection endpoint versus the many certificate-related siblings. There are no exclusions, no prerequisites, and no indication of scope (e.g., team-wide vs. relationship-scoped).

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