List non-secret Temporal client certificate metadata

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile needs no repetition. The description does add one behavioral fact beyond that: results contain only non-secret metadata (i.e., no private key material is returned), which matters for an agent deciding whether it can surface the output. It stops short of describing result shape, pagination, or empty-result behavior, and there is no output schema to fill that gap.

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 a single front-loaded sentence with zero filler, which is structurally clean. But the brevity comes from under-specification rather than economy — the sentence duplicates the title and leaves out information an agent needs.

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 two-parameter, one-required tool with no output schema and no annotations explaining scope, the description leaves the required 'cluster' argument and the optional namespace filter completely unaddressed. An agent can guess it lists certificates but cannot tell what to pass or what it will receive.

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 0% on the two top-level parameters: 'cluster' is required and has only a regex/max-length constraint with no prose, and 'namespace' is an unexplained optional ref. The description says nothing about what cluster identifies, whether namespace filters results, or what happens when namespace is omitted, so it fails to compensate for the coverage gap.

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?

Tautological: description restates name/title.

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 when-to-use guidance, no prerequisites, and no mention of any alternative or related tool. An agent gets no signal about whether this must be paired with a cluster lookup or scoped to a namespace, nor when to prefer another sibling.

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