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

readOnlyHint=true already establishes the safe-read profile, so the bar is lower. The description usefully adds the return payload contents and the underlying endpoint (GET /jobs), but says nothing about pagination behavior, default page size, or result caps despite page/page_size parameters being present.

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 short sentences, with the action and its filters front-loaded, then the payload, then the API reference. The "Housecall Pro: GET /jobs" line is borderline redundant but is a compact source-of-truth pointer, so the text earns its place overall.

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 correctly compensates by describing what each returned job carries (customer, address, notes, schedule, employees, totals). For a 13-parameter list tool it is nearly complete, missing only pagination/default-sort behavior.

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 all 13 parameters are already documented and the baseline is 3. The description's phrase "scheduled window, customer, assigned employees and work status" loosely maps onto those params but adds no format, default, or interaction detail beyond the schema.

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") and enumerates the filter dimensions plus the payload shape, so an agent immediately knows this is the collection endpoint. It does not explicitly contrast itself with the sibling housecall_get_job, so the list-vs-single distinction is implied by "jobs" rather than stated.

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?

The filter list implies when to reach for this tool (e.g. filtered retrieval by window, customer, employee, status), but there is no explicit when-to-use guidance and no exclusion such as "use get_job for a single job" or any note about pagination defaults when omitting filters. Usage is inferable but not spelled out.

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