nexo_credential_get

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

No annotations provided; description carries full burden. It only states 'Get,' which implies a read operation, but does not disclose behavioral traits such as idempotency, whether credentials are cached, authentication requirements, or error behavior (e.g., missing service or key). Insufficient for safe agent use.

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?

Extremely concise: one sentence with no superfluous words. All content is directly relevant despite limited detail.

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?

Output schema is absent; the description does not explain return values (e.g., credential values format, behavior when key is empty vs specified). For a retrieval tool, this leaves significant gaps in agent understanding.

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%; both parameters (service, key) are described in the schema. The description adds no additional meaning beyond what the schema provides. Baseline score of 3 is appropriate.

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?

Clear verb-object structure: 'Get credential value(s) for a service.' The description specifically identifies the resource (credentials) and distinguishes this tool from sibling CRUD tools (e.g., nexo_credential_create, nexo_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?

Minimal guidance. The description states the function but does not explicitly indicate when to use this tool versus alternatives like nexo_credential_list (which might list credentials without retrieving values) or when read access is appropriate. Usage is implied by the name but lacks explicit context.

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