get_account_mtls_certificate

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

With no annotations, the description carries the full burden, but it only restates the get operation without disclosing permissions, absence of side effects, pagination, error behavior, or whether the returned details include sensitive certificate material. 'Get details' provides minimal read-only inference but no substantive behavioral context beyond the name.

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. It is appropriately concise for a simple get operation, though it sacrifices some useful context for brevity.

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?

This is a low-complexity tool with a fully documented two-parameter schema, so the description is minimally viable for invocation. However, without an output schema or annotations, the vague term 'details' leaves the return shape unknown, and the huge sibling list increases the need for at least one sentence of routing context.

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%, with both account_id and certificate_id described in the input schema. The description adds little beyond confirming the certificate belongs to an account, so the schema carries the parameter meaning. Baseline 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 names the exact verb ('Get details') and resource ('account mTLS certificate'), so an agent can tell this is a single-resource read operation. It does not explicitly contrast with list_account_mtls_certificates, but the resource scope is specific enough to disambiguate from other get_* certificate tools.

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?

There is no guidance on when to call this versus list_account_mtls_certificates or other certificate-related tools, and no mention of prerequisite calls. An agent must infer from the tool name alone that this is for fetching one already-known certificate.

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