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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered structurally. The description adds genuine value by disclosing the returned field scope (metadata/approved fields only) and the exclusion set (no secrets, contacts, original files), plus an authorization requirement ('authorised'). It says nothing about pagination or result shape, though limit/offset exist.

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?

Two front-loaded clauses with no filler; the field-scope constraint lands immediately after the action. Efficient, though the second sentence is a fragment that carries a lot of unexpanded meaning.

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 4-parameter, paginated, read-only tool with no output schema and no parameter documentation anywhere, the description leaves too much unstated: it never explains what the returned metadata contains, how paging behaves, or what the target resolves to. The exclusions help, but the definition is not sufficient on its own.

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% and four parameters exist (targetId, query, limit, offset), yet the description explains none of them. It never says what a targetId identifies, what query matches, or that offset/limit page the results, so an agent gets no semantic help beyond the schema's bare types and bounds.

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?

States a specific verb (Read) and resource (certificate metadata) and bounds the scope with 'Metadata/approved fields only; no secrets, contacts or original files.' It does not, however, differentiate itself from close siblings such as list_certificates, get_credential_details, or get_certificate_verification_status, leaving the agent to guess which certificate-shaped tool is right.

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?

'Read authorised certificate metadata through the existing application' gives no when-to-use condition, no prerequisite, and no named alternative. With roughly a dozen certificate/credential siblings, the absence of routing guidance is a real gap.

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