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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds genuinely new behavior: results are sorted by start date, and it names the backing endpoint (GET /api/v3.3/jobs). It still omits pagination/volume limits for a window-scoped list, which is the main remaining gap.

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?

A single front-loaded sentence covering scope, optional filters, and ordering, followed by a compact endpoint reference. No filler, no repetition of the title.

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, filter-based list tool with a fully documented schema and no output schema, the description supplies scope, filters, and ordering. It does not indicate what a job record contains or whether results are paginated, which would matter for an agent processing large date windows.

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% — every parameter (from, to, statuses, property_uids, modified_since) is already documented in the schema, including the required and default behavior of modified_since. The description only restates the date-window/filter semantics at a high level and adds no format or usage detail beyond the schema, so 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 (List) and resource (operational jobs) and even disambiguates what a 'job' is with the parenthetical (cleanings, greetings, maintenance, other services), which separates it from hostfully_list_services. It does not explicitly name a sibling to contrast with, so it lands just short of a 5.

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 description implies usage by noting the date window is the primary scope and properties/statuses are optional narrowing filters, and it states the sort order. It gives no explicit when-to-use/when-not-to-use guidance nor points to create_job or list_services as alternatives.

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