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 adds the 30-records-per-page limit and the underlying GET /{account}/jobs.xml endpoint, which is useful operational context. It stops short of disclosing anything about rate limits, auth, or ordering.

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 the verb and resource, then pagination, then filters, with the endpoint appended. No wasted words.

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 an 8-parameter read-only list tool with no output schema, the description covers pagination and the main filter axes, and annotations cover safety. It is slightly incomplete in not flagging the response-shaping 'only'/'include' options, but those are fully described in the schema.

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 baseline is 3; the description echoes the filter dimensions (schedule window, status, employee, category, job status) but adds no syntax, defaults, or semantics beyond what the schema already documents, and omits mention of the 'only' and 'include' parameters that strongly shape responses.

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 clarifies the resource spans work orders, estimates, and invoices. It also names the filters and pagination, but does not distinguish itself from the close sibling kickserv_list_customer_jobs or from get_job.

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 listed filters (schedule window, status, employee, category, job status) imply the intended use for browsing/filtering jobs, but there is no explicit when-to-use, when-not, or pointer to alternatives such as list_customer_jobs for a single customer's jobs.

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