action_add_secret

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

Annotations are absent, so the description must disclose behavioral traits. It states that the secret must exist in .env, which is a useful prerequisite, but it does not describe side effects (e.g., whether the secret replaces an existing one, whether the operation is reversible), any authentication requirements, or the response format. For a mutating operation, this is minimal disclosure.

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 a single, front-loaded sentence that conveys the core purpose and a key precondition. There is no extraneous information, and the structure is clear and efficient.

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?

The tool is simple with two parameters and a well-documented schema, but the description omits usage context such as when to prefer this over secret_bind, and behavioral details like side effects or error conditions. Although the prerequisite is helpful, the overall guidance is minimal for an agent to call it correctly in all situations.

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 coverage is 100%, so the schema already describes both parameters well. The description adds a prerequisite (must exist in .env) which is an environmental constraint rather than parameter semantics. It does not further explain the meaning of 'secret' or 'endpoint' beyond what the schema provides, so it meets the baseline for high schema 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?

The description clearly states the action: 'Add a secret to an endpoint's context.' It specifies the verb (add), the resource (secret), and the target (endpoint's context). It distinguishes itself from sibling tools like action_add_s3 or action_add_redis which add different resources, and from secret_bind/unbind which likely operate on bindings. The prerequisite about .env also adds specificity.

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 explicit guidance on when to use this tool versus alternatives such as secret_bind or secret_unbind. The description only states a precondition (secret must exist in .env) but does not explain scenarios or indicate when not to use it. With several secret-related siblings, the lack of decision-making guidance leaves the agent to infer the appropriate context.

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