ChangePasswordForCreds

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Change' implies a mutation operation, it doesn't specify whether this requires special permissions, what happens to the old password, whether the change is immediate or requires confirmation, or what error conditions might occur. For a password change tool with zero annotation coverage, this represents significant behavioral gaps.

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, efficient sentence with zero wasted words. It's appropriately sized for the basic function described and gets straight to the point without unnecessary elaboration.

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?

For a password change tool with 2 parameters (including a nested object), 0% schema coverage, no annotations, and no output schema, the description is inadequate. It doesn't explain parameter usage, behavioral implications, success/failure responses, or how this differs from similar sibling tools. The description leaves too many open questions for effective tool invocation.

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 schema has 0% description coverage for both parameters ('id' and 'body'), and the tool description provides no information about what these parameters represent. The description doesn't explain what 'id' refers to (credential ID? username?), what the 'body' object should contain (new password field? confirmation?), or the expected format. With low schema coverage, the description fails to compensate.

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 ('Change the password') and the target ('for a credentials record'), providing a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'ChangeRootPasswordForCreds' or 'ChangePrivateKeyForCreds', which appear to perform similar operations on different credential aspects.

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 provides no guidance on when to use this tool versus alternatives like 'ChangeRootPasswordForCreds' or 'ChangePrivateKeyForCreds'. There's no mention of prerequisites, constraints, or typical usage scenarios, leaving the agent with insufficient context for proper tool selection.

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