Upload attachments

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

With no annotations, the description carries the full burden. It only specifies HTTP method and body type (multipart/form-data) but omits critical traits like file size limits, overwrite behavior, authentication requirements, or error handling.

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 very short but under-specified. It front-loads the HTTP method and endpoint, but the brevity comes at the cost of missing essential details. It is not concise in a helpful way.

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 complexity of a file upload with nested parameters and no output schema, the description is far from complete. It does not explain return values, file type constraints, or behavioral nuances, leaving the agent underinformed.

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 provides some descriptions for nested properties (e.g., file path, filename, fieldName), but top-level parameters (form, path, files) lack description. The description adds 'Body: multipart/form-data' which hints at form parameter usage but does not add significant meaning 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?

The description clearly states the verb 'Upload attachments' and the resource 'tasks' via the endpoint. It is specific to task attachments. However, it does not distinguish from the sibling tool 'weeek_upload_attachments_2' which likely has similar functionality, reducing clarity.

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?

No guidance on when to use this tool versus alternatives (e.g., weeek_upload_attachments_2) or when not to use it. Lacks context for prerequisites or typical use cases.

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