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

Annotations only carry destructiveHint=true, and the 'WRITE' marker plus the raw endpoint are consistent with that. The description adds the meaningful 'estimate' mode behavior (creates the record as an estimate rather than a job) beyond the annotation, but says nothing about auth/permission needs, failure cases, or what happens to fields left unset.

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?

Three tight sentences, front-loaded with the WRITE classification and the essential identifier caveat. No filler; even the endpoint line serves as a debugging anchor.

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 10-parameter creation tool with no output schema, the description never says what the call returns (e.g. the new job's id), which an agent typically needs for follow-up calls to kickserv_add_job_note or kickserv_update_job. Required parameters and the create/update boundary are covered, but the post-call picture is not.

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 coverage is already 100%, so baseline is 3. The description earns above baseline by flagging the high-risk id confusion (internal customer `id` vs. customer number) and by pointing to the sibling tool that supplies customer_id, which the schema does not do.

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+resource ('create a job (work order) for a customer') and marks it WRITE, which cleanly separates it from kickserv_update_job and the various add_* sibling tools. The endpoint (POST /{account}/jobs.xml) confirms the operation unambiguously.

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?

Gives concrete prerequisites: customer_id must be the internal id obtained from kickserv_get_customer (explicitly not the customer number), and job_type_id is the job category. It also explains the estimate flag's behavioral effect. It stops short of naming when to prefer this over kickserv_update_job or how to handle a job that already exists.

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