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

Annotations only declare readOnlyHint=true, so the safety profile is covered, and the description adds the upstream endpoint (GET /jobs) and the shape of each returned job. It says nothing about pagination behavior or result volume despite exposing page/page_size, which limits how useful it is for a 13-param list endpoint.

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?

Three compact sentences: purpose and filters first, then return contents, then the API endpoint. No filler and nothing is buried.

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 what each job carries (customer, address, notes, schedule, employees, totals), and all 13 params are schema-documented. Only pagination/result-size behavior is unaddressed.

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 is already documented in the schema; the description only paraphrases the filter categories (scheduled window, customer, employees, status). Baseline 3 is appropriate since the schema does the heavy lifting.

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 ('List jobs') plus the filter dimensions, so it is clearly a bulk-retrieval tool rather than a mutation. It does not explicitly contrast with the sibling housecall_get_job for single-job retrieval, so sibling differentiation is only implicit.

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?

Usage is implied by the enumerated filters ('filterable by scheduled window, customer, assigned employees and work status'), which tells an agent what scoping is available. There is no explicit when-to-use/when-not statement or routing to housecall_get_job for a single record.

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