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

Annotations only supply destructiveHint=true, leaving the description to carry the behavioral load. It does so by marking the operation as a WRITE and disclosing the return payload (new job's UUID, ClientId, app link), which is genuinely valuable since there is no output schema. It omits any mention of permissions, validation failures, or side effects on existing clients.

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 short, front-loaded sentences: verb+scope, then return values, then endpoint. Nothing is padded, though the trailing 'Workiz: POST /job/create/.' endpoint line contributes little to an agent deciding or invoking the tool.

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 25-parameter creation tool with no output schema and only a destructiveHint annotation, the description covers the essential missing pieces: it declares the write nature and the return payload. It does not note that all 25 parameters are optional or warn about any required minimum input, which is a minor gap.

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 all 25 parameters are already documented in the schema, which sets the baseline at 3. The description's field groupings (schedule, client contact and address, type, source, notes) add light organizational framing but no format or constraint detail beyond what the schema provides.

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 new job') and enumerates the data domains it accepts (schedule, client contact/address, type, source, notes), so the agent knows exactly what the tool produces. It does not differentiate itself from the sibling workiz_create_lead or workiz_convert_lead_to_job, which could also result in a job-like record.

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?

No when-to-use guidance is given. With siblings like workiz_create_lead and workiz_convert_lead_to_job present, the description never states the condition under which a caller should create a job directly rather than create or convert a lead. Usage is only implied by the name.

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