bank_create

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

With no annotations, the description must disclose side effects. It only says 'Create' without mentioning potential errors, permissions, or return values. The note about the Master bank hints at a limitation but does not specify behavior if the name already exists.

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 extremely concise with two sentences, containing no unnecessary information and clearly separating the parameter explanation.

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 simple creation operation with no output schema, the description covers the core action and the parameter adequately. It could mention behavior on duplicate names, but the note about Master partly addresses this. Overall, it is fairly complete.

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?

The schema only defines one parameter 'name' with no description, but the description adds 'Bank name.' which clarifies its purpose. This is sufficient for a single parameter, though more constraints (e.g., uniqueness) are not provided.

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 tool creates a bank to hold events and sounds, distinguishing it from sibling operations like bank_list, bank_rename, and bank_delete.

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?

It explains when to use the tool (to create a new bank) and includes a note that the 'Master' bank always exists, providing a useful constraint. However, it does not explicitly mention alternatives or 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.