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

Annotations already declare destructiveHint=true, and the 'WRITE:' prefix is consistent with that — no contradiction. The description adds the underlying REST endpoint (POST /lead/activate/{UUID}/), but says nothing about permission requirements, reversibility, or what happens to the lead's history. With annotations covering the safety profile, this is adequate but thin.

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?

Two compact fragments, front-loaded with the WRITE classification followed by the action and the endpoint. No filler whatsoever.

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 one-parameter state-change tool with an annotation covering the safety profile, the description supplies enough to call it correctly. It could still note whether the reactivation is reversible or what the lead returns to, which keeps it from a 5.

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% with a single required uuid parameter fully documented ('The lead's UUID (e.g. XYZ56X)'). The description only echoes the UUID via the endpoint path and adds no format or sourcing guidance, 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?

States a specific verb and state transition — 'change a lost lead back to active' — which is clear and distinguishable from siblings like workiz_mark_lead_lost (the inverse) and workiz_update_lead (general edit). It never names those siblings, so it stops short of a 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?

The phrasing 'change a lost lead back to active' implies when to use it (a lead currently in lost state), but there are no explicit exclusions, prerequisites, or pointers to alternatives such as workiz_update_lead. Usage is only implied.

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