Rename Account

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

Annotations declare readOnlyHint=false, indicating a write operation. The description adds valuable behavioral context by explaining that passing null restores the original name, which goes beyond the annotation. It does not mention side effects or permissions, but the annotation covers the core mutating nature.

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 two concise sentences that immediately state the action and include a crucial usage hint. Every word earns its place, with no redundancy or unnecessary detail.

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 rename operation with three clearly described parameters and no output schema, the description sufficiently covers the tool's function and the null clearing behavior. It does not explain expected responses, but that is acceptable given the simplicity and the write-operation annotation.

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%, including the null semantics for customName already documented in the schema. The description repeats the null behavior but adds no new parameter-specific details, so it appropriately 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 uses specific verbs 'Set or clear' and identifies the exact resource 'custom display name for a bank account', clearly distinguishing it from account management and connection tools. The null behavior is also mentioned, which clarifies the full scope of the 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 provides a usage hint about passing null to restore the original name, but it does not explicitly state when to use this tool versus alternatives like 'manage_accounts' or 'toggle_account'. There are no exclusions or alternative recommendations, so the agent must infer context from the tool name and sibling list.

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