Get credential folders

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds minimal context—retrieves folders for the authenticated user—but does not elaborate on pagination, ordering, or security scoping. With annotations covering safety, this is acceptable but not rich.

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, two sentences, with no filler. It is front-loaded with the main verb, but repeats 'credential folders' in both sentences, which is slightly redundant. Still, it earns its place.

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 simple read-only retrieval with no parameters and no output schema, the description is sufficient. It doesn't specify the return format, but that's not critical for a list operation. However, it doesn't mention any authentication context beyond 'authenticated user', which is already implied by the system. Overall, it's 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?

There are zero parameters, so the description doesn't need to explain parameters. The schema is empty, and the description correctly focuses on the operation. Baseline 4 is appropriate for parameterless tools.

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 states the tool retrieves credential folders for the authenticated user, with a specific verb and resource. It is clear and distinguishes from sibling tools like get_all_credentials, though it doesn't explicitly differentiate among the credential-related siblings.

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 its use for retrieving folders, but does not explicitly state when to use this tool versus get_all_credentials or other credential tools. There is no mention of alternatives or exclusions, but the context is reasonably clear given the tool name.

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