vault_store

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

With no annotations, the description carries full responsibility. It discloses that the secret is encrypted at rest and never returned, which is positive. However, it does not mention whether storing a credential with an existing name overwrites or errors, what authentication is required to store, or any rate limits. The transparency is adequate but incomplete.

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 two sentences: the first clearly states the purpose, and the second provides a practical usage hint. Every sentence is meaningful, and there is no wasted text.

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?

This tool has 10 parameters and no output schema or annotations. The description is brief and does not cover important context like what happens on success/failure, whether credentials are overwritten, required permissions, or return values. Given the complexity, more completeness is needed.

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 is 3. The description adds minor value by explaining that provider presets auto-configure auth headers, which the schema also mentions. No additional parameter semantics beyond the schema.

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 'Store a new API credential in the secure vault.' This is a specific verb (store) and resource (API credential), and it distinguishes the tool from siblings like vault_list (listing) and vault_rotate (rotating).

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 hints at usage by mentioning provider presets for auto-configuration, but does not explicitly guide when to use this tool versus alternatives like vault_rotate for updating existing credentials or vault_list for inspection. No when-not or exclusion criteria are given.

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