Assign Task

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

Annotations already indicate readOnlyHint=false and idempotentHint=true, but the description adds useful behavioral context by noting the assignment_group field is updated when provided. This clarifies the operational impact beyond the basic write operation.

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?

The description is two sentences, front-loaded with the action and target, followed by the scope. Every word earns its place, with no redundant information or filler.

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 straightforward assignment operation with good annotations and full schema coverage, the description sufficiently covers purpose, scope, and a key behavioral detail. It does not explain return values, but no output schema exists and this is a simple write action, so completeness is adequate.

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 each parameter already well-documented. The tool description adds limited new meaning—only the optionality of assignment_group—so it relies on the schema for parameter understanding, matching the baseline for high coverage.

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?

The description uses a specific verb 'assign' with a clear resource 'task record' and optional 'assignment group'. It also defines the scope as 'any task-based table', which distinguishes it from sibling tools that target specific task types or actions (e.g., close_incident, add_task_comment).

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 states it works on any task-based table, clearly indicating broad applicability for assignment operations. However, it does not explicitly call out when not to use it or reference alternative tools, leaving some room for interpretation.

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