Create Bundle

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

Goes well beyond the annotations (readOnly=false, destructive=false, openWorld=true) by disclosing uniqueness rules, non-empty requirement, duplicate-set prohibition, default quotas of 5 bundles/10 addresses, that API-created bundles are private, and a 1-credit cost. This is exactly the operational context annotations cannot express.

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?

Front-loaded with the action and the prerequisite, then a compact constraint list. Dense but every clause carries operational meaning; only slight cost is the staccato constraint run-on rather than grouped prose.

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?

No output schema exists, so ideally the description would hint at what a created bundle returns (id/name). Otherwise it covers inputs, constraints, limits, privacy, and cost thoroughly for a 2-parameter mutation.

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%, so both parameters are already documented, including the 'must already be in the address book' constraint. The description adds only the credit cost and privacy note, which are not parameter-level semantics. Baseline 3 is appropriate.

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 (create a named bundle) plus its scope: addresses sourced from the address book. This clearly separates it from siblings like octav_add_bundle_address (adding to existing bundle) or octav_list_bundles.

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?

Explicitly routes the agent to octav_add_address_book_entries as the prerequisite step before calling this tool, and spells out the conditions under which the call will fail (non-unique name, empty bundle, duplicate address set, default limits). No inference required.

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