nexo_credential_list

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

The description clearly states that it returns only names and notes, not values, which is a key behavioral trait beyond the schema. With no annotations, this provides important context. However, it could mention other traits like pagination or rate limits, though not essential for a simple list.

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 extremely concise at one short sentence, front-loaded with the verb and resource, and includes the critical limitation on values. Every word adds value with no redundancy.

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 output schema, the description does not specify the return format (e.g., list of objects, fields). While it states names and notes only, an agent might benefit from knowing the structure. Still, it is adequate for a straightforward list tool with well-named sibling functions.

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 description adds no extra meaning to the 'service' parameter beyond what the schema already provides. The description's mention of 'names and notes only' relates to output, not parameter semantics. Baseline 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?

The description clearly specifies the verb 'list', the resource 'credentials', and the scope: 'names and notes only, no values'. It effectively distinguishes from sibling credential tools (create, delete, get, update) that handle values or mutations.

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 use for listing credential metadata, but does not explicitly state when to use this tool vs alternatives like nexo_credential_get. No guidance on when not to use or which tool to choose for retrieving full credentials.

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