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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered; the description adds genuine context beyond that, including the exact contents returned and the auth requirement ('Needs the user's Cotlet API key with access to this app'). It does not address pagination or freshness, but the added content and auth note are substantive.

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 front-loaded with the resource, but the first sentence ('...line items, total, notes, schedule and every invoice on it') and the second ('...line items with prices, notes, schedule and dispatched team') substantially repeat the same content, adding redundancy without new information.

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?

No output schema exists, so the description carries the return-value burden and does so well by listing the job's fields and the per-invoice status/amount. Auth needs and the pre-progress-invoice use case are included, leaving only minor gaps like response format details.

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 single job_id parameter is documented in the schema. The description does not add syntax or format detail for job_id, so the baseline 3 applies since the schema carries the load.

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 (get) and resource (one job), and enumerates the returned content: customer, service address, line items with prices, notes, schedule, dispatched team, and each invoice with status and amount. This clearly distinguishes it from the sibling list_jobs (returns one vs many) and get_invoice (job-level vs invoice-level).

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?

Gives an explicit workflow trigger: 'Use it before creating a progress invoice,' naming the sibling housecall-pro_create_progress_invoice as the follow-on action. It stops short of stating when-not to use it (e.g., vs get_invoice), so it's clear context without full exclusion guidance.

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