fleet_certificate_list

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

Annotations already declare readOnlyHint and idempotentHint, so the description's read-only statement is partially redundant. However, it adds the paginated envelope field names and the defensive-read gotcha, which are valuable behavioral insights beyond the structured hints.

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 well structured: a bold [READ] prefix, a concise purpose sentence, a return-format note, a gotcha, and an Args section. Every sentence carries useful information, and no filler is present.

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?

Despite having no output schema, the description covers purpose, when to use, the return envelope, parameter behavior, and a behavioral gotcha. This is sufficient for an agent to select and safely invoke the tool for a read-only listing operation.

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 0%, but the description fully compensates by explaining `limit` (max certificates, default 50, None returns all) and `target` (Aria/VCF target name from config, default omitted). This gives actionable meaning beyond the bare schema definitions.

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 begins with "[READ] List certificate status and expiry across the VCF fleet," which clearly identifies the verb, resource, and scope. This distinguishes it from all sibling tools, none of which deal with certificates.

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 states when to use it: "Use this to spot certificates that are expired or expiring soon across all VCF components managed by Operations 9.1." It does not explicitly name alternatives or exclusions, but the use case is clear and well contextualized.

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