Update credential

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

The description adds the behavioral disclosure that secret material is kept out of output and logs, which is beyond what annotations provide (destructiveHint=true). However, it does not mention other behavioral aspects like mutability, permissions, or side effects.

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 concise at one sentence, front-loading the main purpose. It is efficient but could slightly benefit from structuring to separate metadata and value updates.

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 complexity (7 parameters, nested objects, partial data flags), the description is too brief. It does not explain how to use the parameters, especially the 'data' field, or clarify the 'isPartialData' flag. Output schema exists but does not compensate for missing usage context.

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 0%, meaning no parameter descriptions exist in the schema. The description does not provide any additional meaning or guidance for the 7 parameters, including the required 'credentialId' or the complex 'data' object.

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 verb 'Update' and resource 'credential metadata or values', distinguishing it from sibling tools like delete, schema, test, and usage. However, it does not explicitly differentiate from other update-like tools.

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 tool versus alternatives, no prerequisites, and no conditions for usage. The description merely states what it does without context.

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