attach_file_to_task

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

Discloses important behavior: automatic project_id resolution, file size limit and early validation error. No annotations provided, so description carries the burden. No contradiction.

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?

Concise and well-structured: starts with purpose, then lists key rules (parameters, size, error, return value). Every sentence adds value.

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?

Covers return format, parameter rules, and error condition. Missing context like task existence check or permissions. Output schema not provided, but return described.

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?

Description adds meaning beyond the empty schema by naming parameters and usage rules. Schema coverage is 100% but parameters are missing, so description partially compensates.

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?

Clearly states the tool uploads a file to a Kanboard task. Distinguishes from siblings like delete_task_file. However, the input schema is empty despite parameters being mentioned, causing a disconnect.

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?

Provides explicit guidelines: use either file_path or content_base64, not both; maximum file size; when VALIDATION_ERROR occurs. Lacks explicit when-not-to-use or alternatives.

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