start_transfer_4473

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

With no annotations, the description carries the behavioral disclosure burden and does well: it discloses the server-side invoice construction, FastBound 4473 opening, FFL-dealer refusal, and mentions confirm=true. It does not fully explain the side effects of confirm or whether the invoice is submitted vs. just built, but the key behaviors are visible.

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?

Three dense sentences, each earning its place: the first defines the core action and invoice structure, the second explains how to source fee parameters, and the third specifies a key constraint. Information is front-loaded with no fluff.

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 tool with 7 parameters, no annotations, and no output schema, the description covers the core workflow but leaves gaps: return values, error behavior, and the roles of pos_profile and invoice_name are not addressed. It is adequate for a knowledgeable agent but not fully self-sufficient.

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 0%, so the description must compensate. It adds meaning for fee_item and fee_amount (source them from get_transfer_config), and hints at serials ('per gun') and customer ('customer-transfer', FFL refusal). However, pos_profile and invoice_name are left unexplained, and the exact relationship between fee_amount and the retrieved default fee is not clarified.

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 states a specific action ('Start a customer-transfer 4473') and explains exactly what happens server-side: building a transfer POS Invoice with a $0 line per gun plus a Transfer Fee line, and opening the FastBound 4473. It distinguishes this from sibling tools by emphasizing 'customer-transfer' and noting FFL-dealer customers are refused.

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 clearly indicates this is for customer transfers and explicitly says FFL-dealer customers are refused server-side, giving a clear when-not-to-use condition. It also instructs the agent to retrieve fee_item and default fee via frappe_run_method, but does not name an alternative tool or explicitly contrast it with start_4473 or manager_override_4473.

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