post_issue_task

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

Annotations already declare destructiveHint=true, openWorldHint=true, idempotentHint=false, and readOnlyHint=false, so the safety profile is covered. However the description adds nothing beyond that: it does not say the body fields are required, what auth or permissions are needed, or that creation is non-idempotent and will produce duplicates if retried.

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, but the second is a near-verbatim duplicate of the first with one extra clause, so it wastes the little space available. It is front-loaded and short, but the repetition is not earning its place.

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 a nested required body, 0% schema description coverage, no output schema, and a destructive/non-idempotent mutation, the description should at minimum enumerate the required fields and warn about duplication on retry. It omits both, so an agent cannot invoke this correctly from the description alone.

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 0% and the input is a nested object with three required body fields (assigned_user_id, description, expires_at). The description only alludes to the issueId path parameter via 'unique identifier' and says nothing about the required body payload, leaving the burden entirely unmet.

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 states a clear verb and resource (create a task for an issue), but the second sentence only restates the first with the phrase 'using its unique identifier' added. It never distinguishes this from put_issue_task, delete_issue_task, or get_issue_task, so an agent gets the what but no disambiguation.

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?

There is no statement of when to use this tool versus the sibling CRUD tools (put_issue_task, delete_issue_task) or get_issue_tasks. No prerequisites, no context about when task creation is appropriate. The only guidance is the implied 'create' semantics.

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