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

With no annotations, the description carries the full behavioral burden for a mutation tool. It implies a partial update ('and/or'), but never states whether this requires write permission, whether it is idempotent, what happens to unspecified fields, or whether reopening a rejected issue is allowed. The 'and/or' hint is the only behavioral disclosure.

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?

A single front-loaded sentence with no filler; the verb and both mutable targets appear immediately. The nested parenthetical makes it slightly dense to parse, but nothing is wasted.

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 three-parameter mutation tool with no annotations and no output schema, the definition covers the status semantics adequately but leaves the 'important' parameter and the permission/idempotency profile unexplained. It is minimum viable rather than complete.

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 only 33% (only 'id' described), so the description must compensate. It does explain all three status enum values with intent, which adds meaning beyond the bare enum list, but the 'important' boolean is named without saying what it affects, and there is no syntax/format detail beyond the schema.

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?

States a specific verb ('Set') and resource state ('status of a report') plus a secondary target ('the important flag'), so an agent knows this is a mutation tool. It does not explicitly contrast itself with the read-only siblings (get_issue, list_issues), though the update/read split is self-evident. Minor terminology drift: it calls the resource a 'report' while the tool and schema refer to an 'issue'.

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 parenthetical gives intent for each status value ('resolved after fixing it, rejected when nothing should be done, open to reopen'), which is real guidance on choosing a value. However it says nothing about when to reach for update_issue versus alternatives, nor about prerequisites such as permissions or who may reopen an issue.

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