password_create

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

No annotations provided, so description bears full burden. It mentions the returnSecret parameter defaulting to false for security, which is helpful. However, it does not disclose other behavioral traits like idempotency, permission requirements, or what happens on duplicate titles. Basic but not contradictory.

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?

Single concise sentence of 20 words, front-loaded with the core action. No extraneous information; every word earns its place. Efficient and clear.

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 creation tool with 9 parameters and no output schema, the description covers the basics but omits what the response contains (e.g., created item details) and any error possibilities. Adequate but could be more helpful with a hint about return value.

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 description coverage is 100%; every parameter already has a description in the schema. The tool description reiterates 'optional username, URL, tags, and notes' but adds no new meaning. Baseline 3 per rubric for high 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?

Description clearly states the tool creates a new password/login item in a 1Password vault, specifying optional fields (username, URL, tags, notes). It distinctly separates this creation action from sibling tools like item_delete, item_lookup, and password_read.

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?

Description implies creation use but does not explicitly state when to use vs alternatives (e.g., password_update) or prerequisites. Context from sibling tools helps, but no explicit when-not or guidance on vault access or conflict handling.

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