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 the 30-per-page pagination constant and the underlying endpoint, which is modest but real context. It says nothing about auth needs, rate limits, or what a page boundary means for iteration beyond the count.

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 sentences, both front-loaded: capabilities and filters first, endpoint reference last. No sentence is padding, and the parenthetical glosses (work orders/estimates/invoices, job type) are load-bearing disambiguation rather than filler.

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 8 optional filters and no output schema, the description covers the essentials: scope, pagination, and the filter surface. It could be stronger by noting that responses can be trimmed with the 'only' column selector or that embedded relations come from 'include', though the schema does document both.

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% with 8 documented optional parameters, so the baseline is 3. The description does add one clarifying mapping — 'category (job type)' — which helps connect job_type_id to domain vocabulary, but it does not explain how the filters compose or interact.

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, and usefully clarifies that 'jobs' in Kickserv spans work orders, estimates and invoices — a genuine disambiguation of the domain term. It stops short of naming siblings, so an agent cannot tell from this text alone when to prefer kickserv_list_customer_jobs over this tool.

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 enumerates the filter axes (schedule window, status, assigned employee, category, job status), which implies the situations the tool handles, but it offers no when-to-use guidance, no exclusions, and no pointer to alternatives such as kickserv_list_customer_jobs or kickserv_get_job for single-record retrieval.

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