inject

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

With no annotations, the description carries the full behavioral burden, but it only says 'inject', implying a write without disclosing whether the input is overwritten, whether confirmation is required, or whether force can replace an existing output. It also omits that confirm must be true for the write to execute and that fileMode and force affect file-system behavior.

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 sentence with no filler, front-loaded with the action and target. It earns its place without repeating parameter names or schema details.

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 six-parameter file-writing operation with no annotations and no output schema, the description omits essential context: output-file behavior, confirmation semantics, overwrite safety, and template reference format. The schema covers parameter mechanics but not the operational context an agent needs to invoke the tool safely.

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 only the high-level notion that inFile is a template and that secrets come from Proton Pass references. It does not explain the reference syntax or the relationship between inFile and outFile beyond what the schema already states.

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 ('inject'), a data source ('Proton Pass references'), and a target ('a template file'), making the core purpose clear and broadly distinguishing it from item-management and vault tools. It does not clarify whether the template is modified in place or written to a separate outFile, so it falls just short of full clarity.

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?

There is no guidance about when to choose this tool over siblings such as run or create_login_item_from_template, and no mention of prerequisites or exclusions. The intended use is only implied by the one-line description, so an agent must rely on inference.

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