List Account Credentials

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

The description mentions the hard limit of 400 credentials, which is an important behavioral trait. However, it does not disclose pagination behavior, authorization requirements, or potential rate limits. Since there are no annotations, the description carries the full burden, and while the cap is useful, more behavioral details would be beneficial.

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 a single sentence that concisely covers all key aspects: what the tool does, the maximum results, the source, and the optional filter. No unnecessary words or redundant 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?

The description lacks an explanation of the output format or fields, and there is no output schema to compensate. It also omits error conditions or limits beyond the 400 cap. For a listing tool, hints about the returned structure would improve completeness, but the description is adequate for basic understanding.

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?

With 100% schema description coverage, the baseline is 3. The description adds the context of 'account owner directory' but otherwise repeats the schema's optional role filter information. It does not provide additional details like the format of the address or the effect of not providing the role, so it adds marginal value beyond the schema.

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 the tool lists up to 400 XLS-70 Credential objects from an account owner directory with an optional role filter. It uses specific verb and resource, and the sibling tool names (e.g., credential_prepare_create, credential_verify) indicate distinct actions, making this tool's purpose unambiguous.

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?

It explicitly states when to use the tool (to list credentials visible in an account directory with optional filtering). It does not explicitly state when not to use or alternatives, but the context from sibling tools implies that for creating, verifying, or deleting credentials, other tools should be used. This provides sufficient guidance for most use cases.

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