secret_bind

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

With no annotations, the description carries the full behavioral burden. It discloses the atomicity (all-or-nothing) and the fact that it operates on an existing secret, creating a ctx.<SECRET> binding. However, it does not mention what happens if the secret doesn't exist, whether existing bindings are overwritten, or any permission requirements. These are important side-effect details for a mutation tool.

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, well-structured sentence with no waste. It front-loads the key action ('Atomically bind') and packs in all essential context: the secret is existing, multiple endpoints, and the resulting binding name. Every word earns its place.

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 two-parameter tool with no output schema and no annotations, the description covers the core operation well. It explains the atomicity, the source (existing secret), the target (multiple endpoints), and the naming convention. Missing details like failure handling or overwrite behavior are minor given the tool's simplicity and the strong schema coverage.

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 both parameters are documented in place. The description adds semantic value by clarifying that 'secret' refers to an existing .env secret and that 'endpoints' receive the secret as ctx.<SECRET>. This goes beyond the schema's syntactic descriptions, helping an agent understand the domain meaning.

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 ('bind'), a specific object ('one existing .env secret'), a target ('multiple OpenServerless endpoints'), and the resulting representation ('as ctx.<SECRET>'). It clearly distinguishes from sibling tools like secret_unbind and action_add_secret by focusing on the atomic binding action.

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 usage: you have an existing secret and want to attach it to multiple endpoints. However, it doesn't explicitly mention when not to use it or contrast it with alternatives like action_add_secret or secret_unbind. For an agent, the 'existing' qualifier hints at prerequisites, but no explicit routing guidance is given.

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