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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuinely non-structural context: the required Cotlet API key with app-level access, and the fact that every item carries the job_id needed by three specific other tools. It stops short of describing pagination behavior beyond the schema's page parameter.

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?

Roughly four sentences, all information-bearing, with the filter capability front-loaded. Minor deductions for the opening noun-fragment ('Jobs with number, status, customer...') which reads like a field dump rather than a sentence, and for slight ordering where the auth requirement lands last rather than near the top.

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?

There is no output schema, so the description usefully compensates by naming the fields returned and, critically, the job_id handoff to get_job/update_job_status/create_invoice. Combined with the API key requirement and the status-name dependency on list_job_statuses, an agent has what it needs. Pagination depth and result ordering remain unaddressed but are minor for a list tool.

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 every parameter (page, status, start_to, start_from, customer_name) is already documented in the schema, including the list_job_statuses provenance that the description repeats. Baseline 3 is appropriate; the description adds only the 'Unscheduled' example and the range semantics already implied by the schema wording.

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 ('Lists jobs') and enumerates the fields each record carries (number, status, customer, assigned techs, start date). It also names the sibling it is not (get_job) and the downstream tools the returned job_id feeds (update_job_status, create_invoice), so an agent can distinguish it from get_job without opening either schema.

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 concrete filter conditions — status, customer, start date range — with a worked example ('every job in Unscheduled'), and points to list_job_statuses as the source of valid status names. It never explicitly states when to prefer this over siblings like list_customers, but the contextual framing is clear enough for routing.

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