upload_work_item_attachment_from_url

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

With no annotations, the description carries the full transparency burden. It discloses that the MCP server downloads the file server-side and uses the standard three-step presigned S3 flow, and warns about SSRF-related URL restrictions. This goes beyond basic function but doesn't discuss error behavior, size limits, or side effects.

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 well-structured with a clear action statement, process explanation, constraints, and organized Args/Returns sections. Every sentence adds necessary detail without verbosity.

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?

The description covers the process, constraints, all parameters, and return value, making it quite complete for its complexity. It lacks explicit error handling or size limit details, but the core information needed for using the tool is present.

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 input schema has zero descriptions, but the description compensates fully. It explains each parameter: project_id and work_item_id as UUIDs, url with examples (GitHub raw, S3, direct download), and name as an override with default behavior (filename from URL path). This far exceeds schema coverage.

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 the exact action: 'Fetch a file from a public URL and attach it to a work item.' It clearly identifies the resource (file via URL to work item) and distinguishes from sibling tools like list_work_item_attachments and get_work_item_attachment_download_url. The mention of the S3 flow adds specificity.

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 provides clear usage context: it is for attaching files from public URLs, and explicitly defines when-not (URL must be publicly accessible, no private/internal addresses). However, it does not name alternative tools for other attachment scenarios, so it stops short of the most explicit 'use instead' guidance.

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