list_access_certificates

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

With no annotations, the description carries the burden of behavioral disclosure. It does convey that this is a read-only listing operation scoped to an account, which is useful. However, it does not mention pagination, return shape, ordering, or any other behavioral characteristics, leaving some ambiguity for a list endpoint with no output schema.

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, front-loaded sentence with no filler. Every word contributes to identifying the operation, resource, and scope.

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?

The tool is structurally simple with one required parameter and no output schema, so a short description is acceptable. However, the ambiguity with the nearly identical sibling list_account_mtls_certificates and the lack of any return or pagination detail make it only minimally complete for an agent selecting among many similar list tools.

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 already describes account_id as 'The account ID' with 100% coverage. The description's phrase 'for an account' lightly reinforces the account-level scope but adds no meaningful detail beyond the schema, so the baseline score of 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?

The description states a specific verb ('List'), resource ('Access mTLS certificates'), and scope ('for an account'). It is clear about the basic operation but does not distinguish itself from the very similar sibling 'list_account_mtls_certificates', so it stops short of full 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?

No guidance is given about when to use this tool versus alternatives such as list_account_mtls_certificates, list_custom_certificates, or list_client_certificates. The name and description imply the use case, but the confusing sibling overlap makes the lack of explicit routing a real gap.

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