list_fleet_password_accounts

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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds behavior those annotations cannot express: the rotation endpoint is deliberately unwired, so the tool can never rotate or set a password, and response field names are read defensively with unknown fields degrading to empty. That last point is a genuine, non-obvious runtime trait an agent needs.

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 the [READ] tag and a one-line purpose, then a usage sentence and a gotcha. The read-only sentence is slightly redundant against the annotations and could be tighter, but every clause still carries usable information.

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 usefully enumerates the returned per-account fields (username, resource, status, expiry, last_rotated), notes the paginated envelope, and warns about defensive field parsing. An agent has everything needed to call it and interpret the result.

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 the schema already documents limit and target fully. The description only alludes to a 'paginated envelope' and adds no syntax or defaulting detail beyond the schema, making the baseline 3 appropriate.

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 (List) and resource (managed password-account status across the VCF fleet) with a bracketed [READ] marker. An agent can immediately distinguish it from siblings like list_fleet_certificates and list_fleet_domains, which share the fleet-listing pattern but cover different assets.

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 an explicit when-to-use: reviewing 'which fleet accounts Operations manages and their rotation/expiry status.' It also clarifies a boundary (no rotation here), though it doesn't name a competing sibling or state when a different listing tool is preferred, so it stops short of full routing guidance.

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