provider_trust_certificate

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds no behavioral context beyond that — notably it doesn't warn that non-idempotent means re-adding the same certificate/alias may create a duplicate or conflict, nor does it describe side effects or return behavior.

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?

One short sentence with the endpoint appended, front-loaded and waste-free. It is efficient, though the brevity is part of the under-specification problem rather than a virtue.

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?

This is a state-mutating, non-idempotent operation with no output schema, yet the description covers only what the tool does at the highest level. Missing are the mutation's consequences (duplicate handling, effect on existing trusted certificates), required authorization, and what the call returns or how failures surface.

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 100%: the nested body properties alias ('Name, case insensitive') and certificate ('PEM encoded certificate...') are documented in the schema, and the optional id is typed. The description adds nothing beyond the schema, so the baseline of 3 applies.

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 ('Add to list of currently trusted certificates') plus the underlying POST endpoint, so the agent can tell this is a trust-store write operation. However, it does not differentiate itself from the visible sibling provider_query_trusted_certificates, which an agent could easily confuse it with.

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?

No guidance on when to use this versus provider_query_trusted_certificates or provider_add_certificate_library_item, and no prerequisites (permissions, org scope, whether the cert must be pre-validated) are stated. The usage is only implied by the verb 'Add'.

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