nexo_credential_get

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

No annotations are provided, so the description carries full burden. It does not disclose any behavioral traits such as authentication requirements, error handling, rate limits, or side effects. This is insufficient for an agent to understand the implications of using the tool.

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, very concise and front-loaded with the key action. It is appropriate for a simple getter tool, though it could be slightly more informative without losing brevity.

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 the tool's simplicity (2 parameters, no output schema) and good schema descriptions, the description is minimally adequate. However, it lacks details on expected return format, error conditions, and behavioral context, making it less complete for an agent to reason about edge cases.

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 input schema provides clear descriptions for both parameters, achieving 100% coverage. The description adds minimal extra meaning beyond 'value(s)' implying return of values. Since schema coverage is high, the description does not need to compensate, but it adds little additional semantics.

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 clearly states the action (Get), resource (credential value(s)), and scope (for a service). It effectively distinguishes its purpose from sibling tools like create, delete, list, and update.

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?

While the description implies usage for retrieving credential values, it provides no explicit guidance on when to prefer this tool over alternatives like nexo_credential_list or nexo_credential_get. The schema hints at optional key to return all or specific value, but no direct comparison with siblings.

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