list_ssl_certs

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds genuinely non-structured behavior: the call returns Name, Subject, Expiry and Type per certificate and cannot be paged or filtered, which warns the agent about unbounded result size on large inventories. Minor deduction because the returned fields partially duplicate the existing output 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?

Three short sentences, front-loaded with the read-only nature and the resource, then the return shape, then the routing rule. Every sentence earns its place and nothing is repeated.

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 zero-parameter, read-only list tool with full annotation coverage and an output schema, the description supplies everything needed: what it returns, that it cannot be filtered or paged, and when to prefer the sibling. No material gap remains for an agent to call it correctly.

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 tool takes zero parameters, so per the rubric the baseline is 4. The description correctly implies a no-argument full-enumeration call and adds no misleading parameter guidance, but there is nothing parameter-level left for it to clarify.

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 ('List SSL/TLS certificates stored on the AVI Controller') and immediately scopes the result set to the AVI Controller. The inclusion of '[READ]' plus the explicit naming of the sibling it is not (check_ssl_cert_expiry) lets an agent distinguish it from the other list_* tools without opening a 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?

Gives explicit when-to-use ('inventory or a certificate's exact name') and names the alternative with its selecting condition ('use check_ssl_cert_expiry instead for only the ones expiring soon'). It also warns that the call cannot be paged or filtered, which tells the agent not to look for filtering parameters.

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