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

With no annotations, the description does real work: it discloses the computation method (parts at cost + labor minutes × default hourly), that two margin figures are returned (price and member price), the permission requirement, and explicit edge-case behavior — uncosted parts or labor rates are surfaced in a 'missing' list. It stops short of stating this is a read-only computation or commenting on caching/freshness, which keeps it from a 5.

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?

A single dense sentence that front-loads the core answer (

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?

An output schema exists, so return values need no explanation, and the description covers purpose, computation, permission, and a failure mode. The only real omission is any hint about the undocumented item_id parameter, which leaves an agent to guess how to source it.

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% and the single required parameter (item_id, uuid) is never mentioned in the description. The reader can infer the id refers to the flat-rate task being costed, but the description adds no format, lookup, or sourcing guidance to compensate for the undocumented 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?

It states a specific computation over a specific resource: cost of a flat-rate task broken into parts-at-cost plus labor minutes at the default rate, with margin at both price tiers. This is clearly distinguishable from the general costs_job/costs_jobs siblings by its per-task, pricebook framing, though it never names those siblings explicitly.

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?

Usage is implied rather than stated: an agent can infer this is the tool for pricing a flat-rate task before quoting. The description adds a useful access precondition ('needs see_costs', owner or office), but gives no explicit when-not-to-use or pointer to the costs_job/costs_jobs alternatives.

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