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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely new context: the exact fields returned, that the invoice number appears only 'once it is invoiced', and that a Cotlet API key with app access is required. Rate limits and error behavior are unstated.

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?

Front-loaded with purpose, but the field list is enumerated twice in successive sentences ('description, location, techs, products, services, notes and charges' then again as 'location, assigned technicians, products, services, other charges, notes'), which is wasted repetition in an otherwise short description.

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, the description carries the return-value burden and does so by naming the returned components. Auth requirement and the invoice-number-conditional detail round it out. Minor gaps remain around pagination or lookup-failure behavior, but nothing an agent needs to invoke it correctly is missing.

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-schema as 'Job ID from list_jobs'. The description adds no format, sourcing, or token-syntax detail beyond that, so the baseline of 3 applies.

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+resource ('Get job') and enumerates the returned payload (location, techs, products, services, charges, invoice number). 'Returns one job' implicitly separates it from service-fusion_list_jobs, though it never names that sibling, so differentiation rests on inference rather than an explicit contrast.

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 a concrete when-to-use with a named downstream tool: 'Use it to check the status and charges before create_invoice.' That is a real routing cue. However, it offers no when-not-to-use and does not distinguish itself from service-fusion_list_jobs or service-fusion_get_estimate.

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