upload_temp_attachment

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

Annotations only declare readOnlyHint=false and destructiveHint=false, so the description adds real value by disclosing that this is a staging operation whose handle is temporary and single-use ('usable once'). That non-obvious constraint is exactly what an agent needs to sequence calls correctly.

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, front-loaded with the operation and scope, then the return value and downstream consumers. No filler; every clause carries signal.

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?

With no output schema, the description correctly carries the return-value burden ('Returns a temp id usable once') and names the consuming tools. The single-use and temporal nature are covered, though the id's validity window/expiry and failure modes are left unstated.

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 100% (both filePath and filename are documented in the schema), so the baseline is 3. The description adds no per-parameter format or override details beyond what the schema already provides.

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+resource ('Upload a temporary file') and immediately disambiguates from sibling uploads with the parenthetical '(not yet attached anywhere).' An agent can distinguish this from upload_issue_attachment and add_entity_attachment without opening any schema.

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 description gives clear downstream usage: the temp id feeds into create_issue attachmentIds, add_comment attachmentIds and entity attachments. It implies the pre-requisite workflow rather than stating explicit exclusions ('use X instead'). Strong context, but no explicit when-not guidance.

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