list_fleet_certificates

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

Annotations already declare readOnlyHint/idempotentHint, so the bar is lower, but the description still adds real value: it states the operation will not 'renew or replace any certificate' and discloses a non-obvious gotcha that absent response fields render as empty rather than erroring. The return envelope is also spelled out.

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?

Front-loaded with a [READ] tag and the core purpose, then usage, return shape, safety note and gotcha in tight sentences. The field enumeration is slightly long but earns its place given there is no output schema.

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?

With no output schema, the description compensates by naming the returned per-certificate fields and the pagination envelope plus a truncation hint. Combined with the read-only and defensive-read notes, an agent has everything needed to call and interpret this 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?

Schema description coverage is 100%, so both parameters (limit, target) are fully documented in the schema. The description adds no parameter-level syntax or format beyond the paginated envelope reference, matching the baseline for a schema-complete tool.

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 certificate status and expiry') scoped to 'across the VCF fleet', which cleanly separates it from the adjacent fleet siblings (list_fleet_password_accounts, list_fleet_domains) by resource type. An agent can identify the tool 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?

Gives explicit usage context: 'Use this to spot certificates that are expired or expiring soon across all VCF components'. It does not name alternatives or state when-not to use it, so it stops short of a full routing statement.

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