provider_get_certificate

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds real value by disclosing the return format (PEM-encoded) and the underlying GET path, but says nothing about auth, error behavior for a bad URN, or what happens for non-trusted certs.

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?

Three short lines, front-loaded with the action and the payload type. The first line ('Get specified certificate') largely restates what the second line says better, so there is minor redundancy but no bloat.

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 simple annotated read-only getter with no output schema, the description covers what is returned, which is the main thing an agent needs. It still leaves the practical gap of how to discover the required trustedCertificate URN and what failures look like.

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%, but the single parameter's schema text is only '(path)', so the description's 'requested URN' and the URI template do the real work of indicating this is the trusted certificate URN identifier. That is a marginal improvement over the schema, matching the baseline 3.

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 and resource ('Get specified certificate') and adds that the return is the PEM-encoded certificate for the requested URN, which distinguishes it from the list-style sibling provider_query_trusted_certificates. It never explicitly names that sibling, but the resource is unambiguous.

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 statement of when to use this versus provider_query_trusted_certificates, provider_get_certificate_library_item, or provider_trust_certificate. At best the phrase 'with the requested URN' weakly implies you must already know the URN, but no path to obtaining it is given.

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