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

Annotations already declare write, destructive, non-idempotent and open-world, so the safety profile is covered. The description earns credit beyond that by spelling out the concrete consequence of non-idempotency ("Creates a new job every call"), which warns the agent against retry loops creating duplicates, and by prefixing "WRITE:" and the POST endpoint. It does not describe permissions or the response body.

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?

Roughly three compressed clauses with the write-scope flag front-loaded first, then required fields, then the status choice, then the non-idempotency warning. Every sentence carries information and nothing is wasted.

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 17-parameter creation tool the description covers the three required fields and the trickiest decision (which status mechanism to use), and annotations supply the mutation profile. The only real gap is that with no output schema it never says what comes back (e.g. the new job id), which an agent may need to chain calls.

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 71%, so the schema already explains most parameters, including the full status enum meanings and the status_id/status_workflow_id pairing. The description restates the three required parameters and the "numeric billing value" quirk but adds no format or constraint detail beyond the schema, so baseline 3 is appropriate.

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 ("create a job for an existing customer") and names the API endpoint (POST /jobs), so it is unambiguously a creation tool distinct from fieldpulse_update_job, fieldpulse_get_job and fieldpulse_list_jobs. It stops short of explicitly naming any sibling, so it does not reach 5.

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?

"For an existing customer" implies the prerequisite that the customer must already exist, and the status clause gives a usable either/or rule (status 1-6 versus status_id + status_workflow_id). But it never says when to prefer this over fieldpulse_update_job, nor what to do before creating (e.g. create the customer first); usage context is implied rather than stated.

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