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

The 'WRITE:' prefix and the POST endpoint corroborate the destructiveHint=true annotation, but the description does not explain what makes a create destructive, nor does it cover permissions, rate limits, or side effects. With annotations already supplying the write/destructive profile, the added context is modest.

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:' operation type, then scope, then the key identifier caveat. No filler; every clause carries information.

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 9-parameter write tool with no output schema, the description covers the action, the key identifier pitfall, and the endpoint, which is nearly everything an agent needs to call it. It omits what the call returns (e.g. the new task id), which would be useful given no output schema.

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 100%, so the schema already documents every parameter, including the important `job_id` vs job_number distinction. The description's restatement of that distinction adds no meaning beyond the schema, so the baseline 3 applies.

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?

Specific verb+resource ('create a task') with the resource disambiguated ('appointment / to-do') and scoped ('on a job and optionally assign employees'). An agent can immediately distinguish it from kickserv_get_task and kickserv_update_job without opening any schema.

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?

States the create context and points to kickserv_get_job as the source for `job_id`, giving clear provenance guidance. It lacks explicit when-not-to-use guidance or a named alternative for related operations (e.g. logging time entries), so it stops short of a 5.

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