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

Annotations declare readOnlyHint=false, meaning the tool is not read-only and may have side effects, but the description explicitly says 'Writes nothing,' which directly contradicts the annotation. No other behavioral detail (e.g., side effects, error cases) is provided; this is an annotation contradiction.

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 brief and front-loaded with the core action, but the trailing 'Pro.' is cryptic and adds no value, creating mild confusion. Otherwise, it uses two sentences with no wasted words, though the contradiction and unclear 'Pro' deductions keep it from being a perfect 5.

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 no output schema, annotations that are not informative, and a description that contradicts them, the definition lacks critical context. It does not explain when to use this tool, what side effects (if any) exist, or how the units (MAJOR/MINOR) map to parameters. The contradiction further reduces the completeness.

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 each parameter (as_of, schedule, tax_rate, issue_date) has clear descriptions. The tool description adds no parameter-specific detail beyond mentioning VAT rate and units, which only loosely relate to tax_rate and the output structure. The schema carries the meaning, so the 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?

The description states a specific action ('build the delivered-and-accepted deliverables'), the target output format ('invoice_create-ready items' and 'quote_create-ready items'), and the units (MAJOR/MINOR). It clearly distinguishes this from sibling tools by referencing the payload purpose and the 'Writes nothing' behavior, so an agent can infer it generates data rather than modifying records.

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 a preparatory role for invoice_create and quote_create by naming those outputs, but it doesn't explicitly state when to prefer this tool over siblings like deliverable_add or delivery_schedule_get. The 'Writes nothing' hint is a safety cue, but no direct comparison or exclusion criteria are given.

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