aap_list_credentials

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

Annotations already flag read-only and non-destructive, but the description adds that secrets are never returned and are masked by AAP, plus the return format. This is useful context beyond the annotations.

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 front-loaded with the purpose. Args and Returns sections are clearly structured with no redundant text.

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 straightforward list operation with a read-only annotation and output schema, the description covers purpose, arguments at a high level, return format, and the masking behavior. It would benefit from explicit alternative references, but is otherwise adequate.

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 description only labels params as 'Pagination and filter options' without detailing individual fields. Schema description coverage is 0% for the top-level parameter, so the description fails to compensate by explaining page, page_size, search, or credential_type semantics.

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?

Description clearly states the tool lists AAP credentials, distinguishing it from credential detail/modify tools. The verb 'List' and resource 'AAP credentials' are specific, and the note about secrets never being returned adds scope.

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?

Description provides no guidance on when to choose this over sibling tools like aap_get_credential or aap_list_credential_types. It only mentions pagination/filter options without referencing alternatives or exclusion criteria.

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