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 the return content and an auth requirement ('Needs the user's Cotlet API key with access to this app'), but nothing about pagination, rate limits, or failure modes.

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 field list is stated twice in near-identical form (once after 'Full job:' and again after 'Returns one job with everything on its page'), which is redundant and wastes space. The purpose is front-loaded, but the duplication hurts efficiency.

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 usefully enumerates the returned fields and notes the auth requirement, which is enough for an agent to call it correctly. It lacks any mention of empty/missing-job behavior but is otherwise complete.

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%, so the single job_id parameter is fully documented by the schema ('Job UUID from list_jobs'). The description adds no parameter meaning beyond that, making baseline 3 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?

States a specific verb and resource ('Returns one job') and enumerates what the single record contains (client, address, time window, line items, total, amount due, payments). It is clear what the tool does, though it does not explicitly name the sibling it differs from (e.g. workiz_list_jobs).

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?

'Use it before invoicing or recording a payment' gives a concrete usage context that selects this tool against payment/invoice actions. No explicit exclusions or named alternatives are given, so it stops short of a 5.

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