get_credential

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

The annotation readOnlyHint is complemented by the explicit statement 'secret data is hidden', which is a behavioral guarantee beyond the schema. This informs the agent that the tool returns only metadata, not the credential secret.

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 conveys the purpose and the key limitation about secret data. Every word earns its place with no 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 get-by-id tool with one required parameter, the description covers the essential points: retrieval of metadata, hidden secrets, and the ID parameter. It doesn't enumerate metadata fields, but given the lack of an output schema and the tool's simplicity, it is sufficiently complete.

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 schema already defines the single parameter `id` with description 'Credential ID' at 100% coverage. The tool description adds no extra meaning about the ID format or how to obtain it, so the baseline score of 3 applies.

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 a specific verb 'Get' and resource 'credential', and specifies that it returns metadata with secret data hidden. This clearly distinguishes it from sibling tools like list_credentials, update_credential, and delete_credential.

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 clearly implies usage for fetching a single credential's metadata by ID. It does not explicitly state when not to use it or point to alternatives, but the sibling context and the one-parameter schema make the intended use obvious.

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