list_certificates

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

No annotations are provided, so the description carries the full burden. It states that the operation lists certificates and supports filtering/pagination, which implies a read-only action. However, it does not disclose return format, authentication requirements, rate limits, or any side effects. It adds some context but is not rich in behavioral detail.

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 a single, well-structured sentence that front-loads the verb and resource. Every word contributes meaning, with no redundancy or filler.

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?

Despite having 5 optional parameters and no output schema, the description is adequate for a simple list operation. The schema provides rich parameter documentation, and the description covers the high-level purpose. It could mention return format or default pagination behavior, but these are not critical for the agent to invoke the tool correctly.

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 coverage is 100%, so the baseline is 3. The description's mention of 'filtering and pagination' summarizes the top/skip/filter parameters but adds no additional semantics beyond the schema, which already provides detailed descriptions and examples for each parameter.

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's function with a specific verb ('List'), resource ('Arc certificates'), and qualifiers ('with optional filtering and pagination'). It distinguishes from siblings like get_certificate (single certificate) and import_certificate (import operation).

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 implies usage: use this tool to list certificates with optional filtering/pagination. It provides clear context for when to use it, though it does not explicitly mention alternatives or when not to use it. Sibling tools like get_certificate are not referenced, but the purpose is self-explanatory.

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