session_store_login

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

With no annotations, the description carries the disclosure burden. It states that credentials are encrypted and stored, and that extension/Pro are prerequisites. It does not explain whether an existing vault entry is overwritten, whether masterPassword is needed for vault access, or what output/errors to expect, so some key behavior is undisclosed.

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?

One focused sentence with no filler; the primary behavior is front-loaded and the prerequisite is appended. Every word contributes.

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 four parameters, no output schema, and no annotations, the definition is incomplete. It lacks parameter-level guidance, overwrite/merge behavior, return value, and failure states, and it does not address the ambiguity with sibling tools.

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 0%, and the description must compensate. It only references 'credentials for a domain,' which roughly maps to domain/username/password, but it never explains domain, password, username, or the optional masterPassword parameter semantics.

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 names a specific action ('encrypt and store'), a clear resource ('credentials for a domain'), and a destination ('the extension's vault'). This clearly separates it from the sibling session_login, which would perform an actual login, so an agent can identify this as a vault-persistence operation.

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 implies the use case: persist credentials in the vault. It also notes the prerequisite 'Requires the extension and Pro.' However, it does not explicitly say when to prefer this over session_login or other sibling tools, nor does it state when not to use it.

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