Update work schedule

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

No annotations provided, so description carries full burden. Discloses partial update via PATCH, limited supported fields, and side effect of reassigning not-yet-started work items on assignee change. Does not cover authentication or rate limits.

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 sentences, each adding essential information: purpose, scope, and caution. No unnecessary words, well-structured.

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?

Adequately describes function, limitations, and side effects for a simple update tool. No output schema, but response type is likely standard update confirmation; missing error handling info but not critical.

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?

67% schema coverage. Description adds meaning for AssigneeUserKey (side effect) and reinforces ScheduleEndDate behavior (null to clear). WorkScheduleKey not elaborated, but compensates for missing schema description on AssigneeUserKey.

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?

Clearly states the action (Update) and resource (work schedule), with partial via PATCH. Distinguishes from sibling tools like create_work_schedule and get_work_schedule.

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?

Explicitly mentions that only end date and assignee can be changed, implying use for these fields only. Lacks explicit comparison to alternatives but provides clear context.

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