Digital Credentials: Get_user_digital_credential

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safe-read profile is covered. The description adds only the mild context that the lookup is implicitly scoped to the authenticated user rather than an arbitrary one, but says nothing about auth requirements, credential state, or what happens when no credential exists.

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?

A single front-loaded sentence with no filler or redundancy. It is appropriately sized, though it errs toward under-specification rather than being padded.

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 with annotations covering the safety profile and no parameters to document, the description is close to sufficient. With no output schema, however, it gives no hint about what a 'digital credential' payload contains or how absence is signaled, leaving a gap.

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, which is the baseline-4 case; the description's phrase 'the current user's' usefully explains why no identifier is accepted.

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 ('Retrieve') and resource ('the current user's digital credential'), which distinguishes it from sibling allotment tools like Get_credential_allotment and from credential lookups like Get_credential. It is clear what the tool returns, though it does not name a sibling it is explicitly not.

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?

No guidance on when to use this versus the many other credential-related siblings (List_credentials, Get_credential, Get_user_by_credential, Get_allegion_credential_allotment). The agent must infer the use case from the name alone.

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