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

readOnlyHint=true already tells the agent this is a safe read. The description adds useful behavioral context — that results are sorted by start date and that property/status narrowing is optional — but says nothing about pagination, rate limits, auth, or result volume.

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 dense sentence that front-loads scope, filters, and sort order. The trailing API endpoint reference ('Hostfully: GET /api/v3.3/jobs') is conventional but adds little for an agent choosing the tool.

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 full schema coverage and no output schema, the description covers purpose, scope, optional filters, and ordering. It could still note result shape or pagination, but nothing essential for a correct call is missing.

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 five parameters (including the modified_since default caveat) are documented in the schema itself. The description only restates the window/property/status filters, adding no format or syntax detail beyond that — baseline 3.

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 enumerates what counts as a job (cleanings, greetings, maintenance, other services). The date-window scope is front-loaded, easily distinguishing it from hostfully_create_job and other list_* siblings.

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?

It implies the usage context (jobs scheduled in a date window, optionally narrowed by property and status), but never states when to prefer this over alternatives or what prerequisites exist. Since there is no sibling jobs-list tool, the practical risk is low, but the guidance is only implied.

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