Upload File

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

Annotations indicate destructiveHint=true; description adds that absolute paths are not echoed and response returns only safe file names. Discloses constraints beyond annotations, though side effects like overwriting are not mentioned.

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?

Single sentence, front-loaded with action, then constraints. No wasted words; every part 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 main constraints (paths root, timeout, return safety). Output schema exists so return values not needed. Could mention error conditions, but sufficient for typical usage.

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 coverage 100% but description adds value: upload root constraint, absolute path behavior, and safe file names. Clarifies the 'paths' parameter context beyond schema description.

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?

Clear verb+resource: 'Set files on an input[type=file]' distinguishes this upload tool from sibling click/type/select tools. Constraint about DP_MCP_UPLOAD_ROOT and safe file names 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?

States that paths must exist under DP_MCP_UPLOAD_ROOT, which is a key precondition. However, no explicit guidance on when to use vs alternatives or when not to use. Minimal but adequate for a specialized upload action.

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