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

The only annotation is destructiveHint=true, so the description must add the operational context, and it does: it discloses that the job's estimate/invoice total is mutated and that no card is charged, plus the underlying endpoint. It omits permission/auth requirements and whether the added charge can be removed afterward.

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 compact sentences, front-loaded with the WRITE marker and the core action, with the disambiguation and the sourcing hint following in priority order. No filler.

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 an 8-parameter mutation with no output schema, the description covers the write semantics and the item lookup, which is the main ambiguity. The remaining gap is `job_charge_type_id`: it is required but the description gives no hint where its values come from (and there is no list_job_charge_types sibling).

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% and the schema already says `item_id` comes from kickserv_list_items, so the description repeats structured data rather than adding to it. It adds nothing about `job_charge_type_id`, the other required field, or how quantity/price_per_unit/discount interact.

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 ('add'), resource ('charge'), and disambiguates the term with a parenthetical ('line item — a product, service or part'), so the agent knows exactly what is being created on a job. The 'WRITE:' prefix immediately separates it from the read/list siblings and from the note-adding tools.

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?

It gives a concrete sourcing instruction ('Pick `item_id` from kickserv_list_items') and an explicit exclusion ('does NOT charge the customer's card'), which steers the agent away from a plausible wrong expectation. It stops short of stating when to prefer this over the note-adding siblings or what job state is required.

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