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

Annotations already establish readOnlyHint=true, so the safety profile is covered. The description goes further by disclosing sort order, the 14-day implicit window, and the 100-record page cap — genuinely useful traits beyond the annotations, though nothing about rate limits or result shape.

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-loads purpose and sort order, then filters, then defaults in a tight two-sentence block with no filler. The trailing 'Workiz: GET /job/all/.' is mild noise but does map the call to the underlying endpoint.

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?

For a read-only list tool with annotations covering safety, the description supplies sorting, default date window, paging limits, and filter semantics. Since there is no output schema, a brief note on returned record shape would have been ideal, leaving a small gap.

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 schema already documents every parameter including the 14-day default for start_date. The description's parameter notes (max 100, offset/records paging, status/open filters) largely restate the schema, so the baseline 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 and resource ('List jobs') plus a distinguishing behavioral trait: results are sorted by JobDateTime descending. It is readily separable from get_job or list_leads, but it never names an alternative sibling for contrast, so it stops short of the 5 bar.

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 usage context: filter by start date, open-only and status, page with offset/records, and the crucial fallback that omitting start_date yields the last 14 days. No when-not-to-use or explicit alternate-tool routing is provided, which keeps it at 4.

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