Get Credential

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

Annotations already declare the tool as read-only and idempotent, lowering the transparency burden. The description adds the id-scoped retrieval behavior but does not disclose details like not-found handling, return format, or authorization requirements. It is consistent with annotations but provides no additional behavioral color.

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, front-loaded sentence with no wasted words. Every word earns its place: action, resource, and retrieval key.

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 read-only getter, the description is nearly complete. It doesn't describe the return value shape or error cases, but the tool's low complexity and strong annotations make the omission acceptable.

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 coverage is 100% and the single parameter credential_id is fully described in the schema. The description's phrase 'by id' reinforces the schema but does not add extra semantic detail about the id format or constraints.

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 ('Fetch') with a clear resource ('a credential') and retrieval condition ('by id'). This clearly distinguishes it from sibling tools like lyzr_credential_list, lyzr_credential_create, and lyzr_credential_delete.

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 usage when a credential id is known and a single credential is needed, but it does not explicitly state when to avoid this tool or mention alternatives. It provides only implied usage context rather than explicit guidance.

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