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

Annotations already establish that this is a non-read-only, non-destructive, non-idempotent write operation. The description adds useful behavioral detail beyond annotations: created status is OPEN, source is admin, and the description becomes the first thread message, with category and severity defaults.

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 dense but front-loads the core action and then supplies necessary enum and default details. The category and severity lists make it longer, but that information is useful and not redundant.

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 five-parameter write tool with annotations covering safety and no output schema, the description is largely complete. It covers creation semantics, defaults, and thread-message behavior, though it leaves task_id and return behavior implicit.

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 low at 20%, so the description carries more burden. It compensates well for the ambiguous category and severity parameters by listing allowed values and defaults, and it explains how description is used, though it does not elaborate on task_id.

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 a specific verb and resource: raising an issue on a task, including the underlying POST endpoint. It does not explicitly distinguish itself from nearby siblings such as update_issue or reply_issue, so it falls short of the top score.

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?

It explains the admin-style creation behavior and marks this as a write-tier tool, but gives no explicit guidance on when to use this versus update_issue, reply_issue, or list_issues. Alternative-routing guidance is absent.

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