create_password

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

The description discloses server-side encryption and notes that customFields replaces all existing fields (though this is odd for a create, it is a behavioral detail). Annotations already indicate read/write, destructive, and idempotent hints, but the encryption note adds value beyond the metadata.

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, well-structured sentence followed by a brief encryption note. It avoids redundancy and uses parallel lists, making it easy to scan quickly.

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?

The description covers the essential information: required vs. optional fields, encryption, and custom field constraints. It does not mention return value or error cases, but those are not required given the absence of an output schema. It is sufficiently complete for an agent to invoke the tool correctly.

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 provides descriptions for several parameters (label, password, folder, hidden, customFields, and customFields.type), and the description text clarifies that username, url, notes, folder id, and favorite are optional. It also gives constraints on customFields (max 20, label/value lengths), compensating for the 56% schema description coverage.

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?

Clearly states the action 'Create' and the resource 'a new password entry'. It also lists required and optional fields, and the name distinguishes it from sibling tools like update_password, delete_password, and list_passwords.

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 makes the purpose obvious, but it does not explicitly explain when to choose this tool over alternatives (e.g., use update_password for existing entries). It also lacks guidance on typical scenarios or prerequisites beyond the required fields.

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