list_dns_credentials

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

Annotations only declare readOnlyHint=true, so the description earns credit for adding that the response contains 'credential metadata (not secret values)' — a meaningful disclosure about what is and is not exposed. It also documents the account/auth prerequisite. It stops short of full transparency only because pagination or result shape details are absent.

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 purpose is front-loaded in one sentence, followed by a compact ACCESS block that gives the two concrete setup paths. Both paragraphs carry useful information, though the ACCESS section is slightly verbose for a no-argument list tool.

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?

With no parameters and no output schema, the description covers what the agent needs: the result nature (metadata, no secrets) and the auth prerequisite. Only minor gaps remain, such as result volume or pagination behavior for an account with many credentials.

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 tool takes zero parameters, so per the rubric the baseline is 4. There is nothing for the description to clarify, and it introduces no misleading parameter implications.

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?

States a specific verb (List) and resource (stored DNS provider credentials) with the scope 'for the authenticated account', which cleanly separates it from create_dns_credential and delete_dns_credential. It does not explicitly name a sibling or contrast with get_dns_providers, so it lands just short of full differentiation.

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 implied by the read-only 'List' framing and by the sibling set (create/delete credentials exist for the mutations), and the ACCESS paragraph gives setup conditions. However, there is no explicit when-to-use/when-not or statement of when to prefer this over get_dns_providers or check_domain_credentials.

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