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

Annotations already declare readOnlyHint=true, and the description adds meaningful behavioral detail beyond them: the 30-records-per-page pagination behavior and the underlying GET endpoint. It still doesn't describe ordering or response shape, but pagination is the key operational fact for iterating results.

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?

Two tight sentences with the purpose and pagination front-loaded and no filler. Every clause carries information the agent needs.

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, single-page list tool with full schema coverage and no output schema, the definition supplies the essentials (scope, page size, endpoint). A note on default ordering or total counts would make it fully complete, but nothing required to call it correctly 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?

With 100% schema description coverage, the schema already documents only/page/include/customer_number, and the page description itself repeats the 30-per-page note. The description adds no semantics beyond what the structured schema provides, so the baseline of 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 (jobs) scoped to 'one customer', which separates it from the broad kickserv_list_jobs sibling. It is clear what the tool returns, though it never names the sibling explicitly to reinforce the distinction.

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?

Usage is only implied by the 'for one customer' scope; there is no explicit when-to-use, when-not-to-use, or alternative routing. An agent can infer it, but the definition leaves the choice between this and kickserv_list_jobs to inference.

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