Add Address Book Entries

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

Annotations declare a non-read-only, non-destructive write, and the description adds exactly the context they cannot: free-plan cap of 50 addresses, a 1-credit cost, the no-op semantics for duplicates (existing label preserved), and that the full address book is returned. That is the mutation behavior an agent needs before spending credits.

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?

Four short sentences, front-loaded with what gets saved, then duplicate behavior, then limits/cost, then return value. No filler and no redundant restatement of the schema.

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?

Covers the mutation semantics, plan cap, credit cost, idempotency on duplicates, and the return value ('the full address book') despite there being no output schema. Nothing material an agent needs before calling is absent.

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% with a single nested array parameter, so the baseline is 3; the description earns extra by noting that each entry takes an optional label and that the address must be a wallet on one of the four named chains, which the schema never says. It does not restate the 1-100 per-request bound, which lives in the schema.

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?

States a specific verb and resource ('Save addresses ... to the address book') plus the supported chain families (EVM, Solana, Starknet, Tron) and the optional label. It also names the sibling octav_rename_address_book_entry for the related-but-different operation, so it is distinguishable without opening any schema.

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?

Explains the already-exists case ('keeps its existing label') and routes the agent to octav_rename_address_book_entry for relabeling, plus states the 50-address free-plan ceiling. It does not explicitly say when to prefer this over creating a bundle or list, but the nearest alternative is covered.

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