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

With no annotations, the description carries the full burden and does well: it discloses that the link is single-use, expires in 30 days, and that no email side effect occurs. It omits the auth/role requirements and whether issuing a new link invalidates prior ones, but the core behavioral traits are covered.

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 compact sentences with zero filler, and the key constraint (single-use, 30-day) plus the manual-sharing caveat are front-loaded. Nothing redundant.

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 single-parameter tool with no output schema and no annotations, the description covers the essential behaviors: what is returned (a link), its lifetime, its single-use nature, and the absence of automated delivery. Only the auth prerequisites and link retrieval details are unstated.

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?

One parameter at 0% schema coverage, so the description must compensate and only partially does: 'cert issuer' implies cert_id identifies the certificate to confirm. It adds no format, provenance, or validation detail for cert_id beyond that inference.

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+resource: obtaining a single-use confirmation link for a cert issuer, with the yes/no purpose made explicit. It is clear what the tool produces, though it does not name or contrast itself against any sibling (e.g. confirm_email or add_cert).

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?

The phrase 'Share it yourself (no email is sent)' implicitly tells the agent this tool only mints the link and delivery is manual, which is meaningful usage context. However, there is no explicit when-to-use trigger or statement of when another confirmation path should be preferred.

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