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

Annotations already cover readOnly, idempotent, and destructive hints (false for all). The description adds meaningful behavioral details: the bundle is decrypted with the provided password, certificates are extracted, and stored with AES-256-GCM encryption. It also specifies the required scope. This goes beyond annotations without contradicting them.

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 efficiently structured with a clear one-line summary followed by brief explanatory details. Each sentence carries value: purpose, process, scope, mapping, and a caution. It is front-loaded and contains no filler.

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?

The description covers the main functional aspects, scope, and OpenAPI mapping. However, it lacks any mention of return values or error scenarios (no output schema exists), and it does not clarify whether uploading replaces an existing certificate or handles duplicate situations. Given the possibility of similar siblings (uploadCertificate), this is a noticeable gap but not critical.

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%, so the baseline is 3. The description mentions the password in the process but does not add any new meaning beyond what the schema already provides for each parameter. No additional context about parameter usage, formats, or constraints is given.

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 clearly states the action (upload a .p12 certificate bundle) and the resource (signer certificate and private key). It explains the process of decryption and encrypted storage. It does not explicitly differentiate from the sibling uploadCertificate, but the .p12 format makes the purpose specific enough.

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 description implies use for .p12 bundles and warns against inventing other paths ('Do not invent other paths'), but it does not explicitly state when to choose this over alternatives like uploadCertificate or mention any prerequisites or conditions. Usage context is implied rather than stated.

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