get_user_credentials

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

No annotations provided, so description handles behavioral disclosure. States it reads /users/{id}/credentials and is read-only, does not create a session. Does not detail auth requirements or rate limits, but adequate for a simple read operation.

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?

Description is 5 sentences, front-loaded with purpose. Each sentence adds value: purpose, use case, API path, argument detail. Could be slightly more concise but not verbose.

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?

Given no annotations and presence of output schema, description sufficiently covers behavior and usage. Lists credential types and reading action. Missing potential details like authentication requirements, but complete for its simplicity.

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 has 0% description coverage; description adds 'Exact username (email)' to the 'username' parameter, clarifying required format. Adds meaningful context beyond the schema's basic type definition.

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?

Description clearly states verb 'List' and resource 'credential types configured for one user'. Examples include password, otp, webauthn. Distinguishes from sibling tools like get_user or get_user_sessions.

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?

Explicitly states 'Use this to check a single user's MFA status'. Provides context that an 'otp' credential means TOTP/HOTP is configured. Does not mention when not to use or alternatives like get_totp_users, but usage is clearly defined.

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