camelot_receipt_itemizer

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

Annotations already identify the tool as idempotent and non-destructiveched. The description adds 'Local browser processing', which meaningfully tells the agent that data is handled client-side and no server-side state change should be expected. No contradiction with the annotations exists.

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 compact and front-loaded with the core actions, followed by the useful 'Local browser processing' note. Minor issues are the redundant 'Receipt Itemizer:' prefix and the double period after 'records', but overall there is no meaningful 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?

With an output schema present, annotations covering safety, and all parameters documented in the input schema, this description provides sufficient invocation context. The only missing piece is explicit sibling differentiation, which is already captured in the usage guidelines score.

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%, and the schema already documents all four parameters including defaults. The description's mention of 'tax breakdowns' adds little beyond the existing salesTax schema description, so the baseline schema-driven score of 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?

The description uses specific action verbs ('Tabulate', 'compute', 'export') and names the concrete resource ('receipt line items'), making the tool's purpose immediately clear. It also differentiates from finance siblings like camelot_expense_log_analyzer by focusing on receipt-specific itemization and tax breakdowns.

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 use for receipt-related itemization and tax computation, but it never explicitly states 'use this when...' or contrasts with possible alternatives like camelot_expense_log_analyzer or camelot_invoice_generator. With many finance siblings present, routing relies mostly on inference from the tool name.

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