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

With no annotations provided, the description carries the burden of behavioral disclosure. It explicitly states 'API key is not exposed', which is a valuable safety-related behavior beyond what the schema shows. The verb 'Get' implies read-only, and the caveat helps agents avoid expecting sensitive data in the response.

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 well-structured sentence with no unnecessary words. The main purpose is front-loaded, and the parenthetical adds important security context without redundancy.

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 one-parameter get operation with no output schema, the description covers the key aspects: what it retrieves and a critical limitation. It lacks explicit return format or error behavior, but given the simplicity, the provided context is sufficient for an agent to select and invoke the tool correctly.

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 0%, so the description must compensate. It mentions 'by ID', which connects the single required `id` parameter to the credential's identifier, but adds no further detail beyond the schema's integer type. The semantics are clear but minimally elaborated.

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 uses a specific verb ('Get') and resource ('provider credential') with a clear scope ('by ID'). It distinguishes from sibling tools like provider_credentials_list by focusing on a single credential retrieval. The parenthetical about API key not exposed adds a unique distinguishing detail.

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 phrase 'by ID' clearly indicates this tool is for retrieving a single specific credential when its ID is known. It provides clear context for usage, though it does not explicitly mention alternatives like provider_credentials_list. No exclusions are stated, but the purpose is unambiguous.

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