Assign Issue

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

Annotations already indicate readOnlyHint=false (write operation). The description adds behavioral context: it uses the dedicated assignment endpoint, raises ValueError in failure modes (read-only mode, client unavailable, user not found), and is more reliable than update_issue. This goes beyond annotations.

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 sentence intro followed by structured Args/Returns/Raises. No redundancy, front-loaded with key benefit. Every sentence serves a purpose.

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?

Given the tool has an output schema (so return values don't need description), and annotations cover safety, the description covers purpose, usage guidance, parameter semantics, and error conditions completely. No gaps for a two-parameter assignment tool.

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%, baseline is 3. The description adds value by explaining that 'assignee' can accept a JSON object string from jira_search_assignable_users and that null/empty string triggers unassignment. This clarifies usage beyond the schema's basic type descriptions.

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 clearly states the action ('Assign a Jira issue to a user'), the resource ('Jira issue'), and distinguishes it from the sibling 'update_issue' by noting it uses a dedicated endpoint and is more reliable. This satisfies the specific verb+resource and differentiation criteria.

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?

Explicit guidance on when to use this tool over the alternative 'update_issue' (which can be silently ignored). Also specifies how to unassign (pass None or empty string) and the acceptable formats for assignee. No exclusions needed beyond this.

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