cloud_list_certificates

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

With no annotations, the description must disclose behavioral traits. It only says 'List', implying a read-only operation, but does not explicitly state that it is non-destructive, safe, or any information about pagination, rate limits, or response shape. The minimal disclosure leaves the agent unaware of key behavioral aspects.

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 very concise (three words) and front-loaded, but it is too brief for a tool with five optional parameters and no schema descriptions. While not wasteful, it under-specifies necessary information, earning an average score.

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?

Given the complexity (5 parameters, pagination) and the existence of an output schema, the description is severely incomplete. It does not mention filtering, pagination, or how results are structured, leaving the agent to guess or rely solely on names.

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?

The input schema has zero parameter descriptions, and the tool description provides no additional meaning about the five parameters (page, per_page, name, type, label_selector). The agent has no clue how to filter or paginate, which is critical for this listing operation.

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 states 'List managed TLS certificates', which clearly indicates a listing operation for a specific resource type (managed TLS certificates). It distinguishes from sibling tools like cloud_get_certificate (single retrieval) and cloud_create_certificate (creation). However, it could be more specific about the scope (e.g., all certificates or filtered).

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 is provided on when to use this tool versus alternatives (e.g., cloud_get_certificate for a single certificate). There is no mention of prerequisites, context, or scenarios where other tools would be more appropriate.

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