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

Annotations only supply destructiveHint=true, so the description meaningfully adds that this is a write/mutation and that the change is reversible by workiz_assign_job. It also discloses the underlying endpoint. It stops short of noting permission requirements or side effects on other assignments.

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 sentences, zero waste, with the WRITE marker front-loaded and the reversibility path immediately following. Every clause earns its place.

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 two-parameter tool with full schema coverage and no output schema, the definition covers mutation nature, reversibility, and the sibling used to resolve the user name. Missing only edge-case behavior such as what happens if the member is not assigned.

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%: UUID and User are both fully documented in the schema, including the 'exact name' constraint and the pointer to workiz_list_team. The description's 'by name' phrasing only restates what the schema already says, so 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?

States a specific verb and resource ('remove a team member ... from a job') with a leading 'WRITE:' marker, and names the inverse sibling workiz_assign_job, so an agent can distinguish it from workiz_assign_job without opening either 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?

Gives clear operating context: the operation is reversible via workiz_assign_job, and the job/member pairing is scoped. It does not explicitly state when to prefer this over e.g. workiz_update_job, but the routing to the inverse tool is explicit.

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