upload_task_attachment

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the core action and parameter constraints. It does not disclose important behavioral traits such as what happens on success (e.g., return value), permission requirements, size limits, idempotency, or conflict handling. The schema's url description mentions rejection of private/loopback hosts, but the tool description itself adds no further behavioral context.

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 consists of two sentences with no wasted words. The first sentence states the purpose, and the second provides essential usage rules. All information is front-loaded and every sentence earns 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 the tool has 7 parameters and no output schema, the description is somewhat minimal. It adequately covers parameter usage but lacks information about the return value, behavior on errors, prerequisites (like task existence), and any side effects. While the schema descriptions fill some gaps, the tool's description could be more complete for a mutation tool.

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 high (86%), so the baseline is 3. The description adds value by clarifying the mutual exclusivity of the three source parameters and the conditional requirement for file_name with base64. This goes beyond the individual parameter descriptions in the schema, which do not explicitly state these interdependencies.

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 uses the specific verb 'Attach' and resource 'file to a task', clearly indicating the action and target. It explicitly lists the three mutually exclusive source types, making the tool's functionality immediately understandable. There is no sibling tool with similar purpose, so differentiation is clear.

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 guidance by stating 'Provide exactly one source' and specifying that file_name is required when using base64. While it does not explicitly mention when not to use this tool or suggest alternatives, no direct alternatives exist among siblings, so the guidance is sufficient for correct usage.

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