lb_delete_ssl

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

No annotations are provided, so the description bears the full burden of behavioral disclosure. It only says the certificate is deleted and a status message is returned; it does not disclose permanence, side effects on forwarding rules or traffic, permission requirements, or idempotency. The mention of ctx for resource change notifications is the only extra behavioral detail, and it is absent from the input schema.

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 compact and well organized: a one-line purpose followed by a short Args and Returns section. It is front-loaded and free of fluff, though the inclusion of ctx in Args adds a small amount of confusion given the schema mismatch.

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 one-required-parameter operation with an output schema, the description covers the core invocation surface. It is less complete contextually because there are no annotations, no usage guidance, and no side-effect disclosure for a destructive operation; an agent can make the call but cannot anticipate consequences or choose it confidently among related LB tools.

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?

The schema has 0% description coverage and only lists a string field, so the description's clarification that load_balancer_id accepts an ID or label (e.g., 'web-lb', UUID) is valuable. It fully explains the only real user-facing parameter. However, it also lists a ctx parameter that does not appear in the input schema, which introduces a minor inconsistency.

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 action and resource: 'Delete SSL certificate from a load balancer.' This is unambiguous and differentiates it from sibling tools such as lb_delete (deletes the load balancer itself), lb_disable_auto_ssl, and cdn_delete_cdn_ssl_certificate. An agent can tell what resource is affected without opening the schema.

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 tool versus alternatives, when not to use it, or prerequisites (e.g., whether the SSL certificate must exist, or what happens if auto-SSL is enabled). The description implies usage only through the verb 'Delete,' but does not mention related options like lb_disable_auto_ssl or cdn_delete_cdn_ssl_certificate.

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