retrieve_secret_list

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

Annotations already declare read-only, idempotent, non-destructive, and open-world behavior. The description adds account scope and filtering context, but does not explain pagination behavior, default sorting, rate limits, or what a response contains.

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 very short and front-loads the operation and endpoint. There is minor redundancy between 'List secrets' and 'List and filter all secrets', but no wasted explanatory 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?

This is a simple list tool with six optional params and no output schema, and annotations already cover safety traits. However, the description omits pagination semantics and return-value context, leaving gaps an agent might need when composing queries.

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 all six parameters are already documented in the schema. The description mentions filtering generically but adds no parameter-specific meaning beyond the schema, such as supported orderBy fields or name/type filtering examples.

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 clearly states a specific verb and resource: listing and filtering secrets in an account. It implies the list scope versus a single secret, but never names or differentiates against the sibling retrieve_secret tool explicitly.

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?

Usage is only implied by 'List and filter all secrets in your account.' The description does not say when to choose this over retrieve_secret, create_secret, or retrieve_secret_audits_list, nor does it mention any exclusions or prerequisites.

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