post_issue_attachment

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

Annotations already declare readOnly=false, destructive=true, idempotent=false, and openWorld=true, so the safety profile is covered. The description adds no behavioral context beyond those annotations, such as the 14MB payload cap, base64-only input, or what happens on duplicate uploads.

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 are used to say the same thing twice; the second is pure redundancy rather than added information. Front-loading is fine, but the repeated clause wastes the whole budget.

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 mutation tool with nested base64 file content, no output schema, and low schema description coverage, the description is too thin. It omits payload size constraints, accepted content encoding, and what the caller gets back after upload.

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?

The phrase 'using its unique identifier' loosely points at the issueId path parameter, but the description adds no real semantic detail. With schema description coverage reported at 0% for the tool, the description should compensate for undocumented parameters and largely fails to do so.

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 first sentence gives a clear verb+resource ('Upload an attachment for an issue'), and calling out 'issue' implicitly separates it from sibling attachment tools like post_test_case_attachment and post_test_result_attachment. However, the second sentence merely restates the same action ('Upload an attachment for an issue using its unique identifier'), adding no differentiating information.

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 guidance on when to use this tool versus the many sibling attachment tools, no mention of prerequisites (issue must exist, file size limits), and no exclusions. The description only asserts what the tool does, never when an agent should reach for it.

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