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

readOnlyHint=true already tells the agent this is a safe read, so the bar is lower. The description usefully adds the pagination unit (30 per page) and the underlying REST endpoint, but says nothing about ordering, filtering behavior, or what the response contains.

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 short sentences: the scoping/pagination fact first, the endpoint reference second. Zero filler and nothing to trim.

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?

A simple, read-only, fully-documented-schema listing tool with no output schema, so the description is nearly sufficient; pagination behavior is disclosed. Missing only lightweight context such as result ordering or the maximum useful page, which the schema's page maximum hints at.

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 `only`, `page`, `include`, and `customer_number` are all documented in the schema itself. The description only echoes the 30-per-page fact already present in the `page` parameter description, adding no new parameter meaning.

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 the jobs') and scopes it to 'one customer', which implicitly separates it from kickserv_list_jobs (all jobs) and kickserv_get_job (single job). It stops short of naming those siblings, so an agent must infer the boundary.

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: the phrase 'for one customer' plus the required customer_number signals this is the customer-scoped listing variant. There is no explicit when-to-use/when-not guidance and no named alternative such as kickserv_list_jobs, so routing depends on inference.

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