upsert_account_nickname

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'save', which indicates a write operation but does not clarify whether this creates, updates, or overwrites an existing nickname. It also does not disclose return values, error conditions, or idempotency, leaving the agent without critical behavioral expectations.

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 sentence that is direct and to the point. It includes a helpful example without any extraneous content. 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?

Given the tool has four parameters, no output schema, and no annotations, the description is incomplete. It lacks information about return values, the upsert semantics (create vs. update), and the purpose of optional parameters. The agent cannot fully anticipate the tool's behavior from this description alone.

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 description explains account_id and gives examples for nickname, but it does not mention the optional 'notes' or 'institution_hint' parameters at all. With schema description coverage at 0%, the description must compensate for all parameters, and it fails to do so for half of them. This leaves the agent unsure of their purpose.

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 ('Save a nickname') and target ('account_id'), with concrete examples ('Chase checking', 'Amex BCE'). This distinguishes it from the sibling tool 'list_account_nicknames', which is for reading nicknames, not saving them.

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 when to use this tool – when needing to assign or update a nickname for an account. It does not explicitly mention the 'upsert' behavior or contrast with listing, but the purpose is clear enough to infer the appropriate context. No exclusions or alternatives are stated, but the context is straightforward.

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