create_login_item

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

With no annotations present, the description carries the full behavioral burden, but it merely restates the operation and does not disclose critical traits: that confirm must be true to execute the write, that agentReason is required for agent sessions, or how vaultName versus shareId resolves. The schema documents the confirm parameter, but the description itself contributes no behavioral context.

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?

A single 9-word sentence with the verb front-loaded and zero filler makes for an efficient, well-structured description. It is terse but not padded; additional behavioral content could be added without sacrificing this structural quality.

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 10-parameter mutation tool with no annotations and no output schema, a one-sentence description is under-specified. Critical invocation context is missing: the confirm=true execution requirement, whether vaultName or shareId is preferred or what happens when neither is given, the agentReason requirement, and routing to the similar create_login_item_from_template sibling.

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%, so the baseline of 3 applies even though the description adds no parameter-level detail. The phrase 'in a vault or share' loosely aligns with shareId and vaultName but does not explain their relationship or fallback behavior. The schema already documents every parameter, so no significant compensation is needed.

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 states a specific verb and resource ('Create a login item') plus a target context ('in a vault or share'), making the core purpose clear and distinguishing it from item-type siblings like create_note_item or create_credit_card_item. It falls short only in not differentiating from the closely named sibling create_login_item_from_template, which also creates login items.

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 is provided on when to use this tool versus its many alternatives. There is no mention of conditions that would favor create_login_item_from_template, generate_random_password, or the other create_*_item tools, and no exclusions, prerequisites, or context signals are given.

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