List stored credentials (metadata only)

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

The description clearly states the tool returns only metadata (usernames/descriptions and IDs) and never secrets, which is a key behavioral trait. There are no annotations, so the description carries the full burden; it adds value by clarifying the output scope and safety (no secrets exposed). It could mention if pagination or filtering is supported, but given zero parameters, it's sufficient.

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?

Two sentences, no wasted words. The first sentence clearly states the action and output, the second adds context for usage. Ideally concise and front-loaded.

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?

The description covers the tool's function, output type, and usage context. Given no parameters and no output schema, it is adequately complete. It could mention that authentication is required (implied) and that the list is comprehensive (no filtering), but not necessary for basic use.

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?

There are no parameters, so the schema coverage is 100%. The description adds meaning by specifying what is listed (metadata) and that secrets are omitted, which enriches the understanding beyond the empty schema. Baseline for 0 params is 4.

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 it lists credential records (usernames/descriptions and IDs) and explicitly notes that secrets are never returned. It also contextualizes the purpose by mentioning that credential IDs are referenced when creating jobs or adding managed servers, distinguishing it from sibling tools like create_job or list_managed_servers.

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 implies usage context by stating that credential IDs are needed for job creation and managed server addition. However, it does not explicitly state when to use this tool versus alternatives, nor does it provide exclusion criteria or when not to use it.

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