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

Adds meaningful context beyond the annotations: it runs without a confirmation prompt, sends nothing to the client, and can be reversed with one more call. This reversibility and side-effect disclosure is valuable for a write tool. It stops short of a full picture (e.g., what happens to overlapping schedules), so not a 5.

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?

Front-loads the core action in the first clause, then layers behavior. All sentences carry information, though there is mild redundancy between 'Assign or unassign team members' and 'Adds team members to a job,' and the trailing API-key sentence reads as boilerplate.

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 three-parameter mutation tool with no output schema and annotations covering the safety profile, the description supplies confirmation behavior, side effects, reversibility, and auth requirements. Only minor edge cases (e.g., duplicate tech_ids, empty array behavior) are left unaddressed.

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 baseline is 3. The description echoes the replace flag behavior ('replaces the current ones when replace is true') and the tech_ids meaning, but adds nothing beyond what the schema descriptions already provide.

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 ('Assign or unassign team members on a job') and clarifies the replace semantics. It does not name or distinguish itself from any sibling tool, but there is no competing assign tool within the Workiz set, so differentiation is largely unnecessary.

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 description explains the two operating modes (add members vs. replace the current ones when replace=true), which implicitly guides usage, but it never states when to prefer assignment vs. rescheduling or any alternative tool, and offers no exclusions or prerequisites beyond the API key note.

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