media_upload

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It states only the basic action and return value, without mentioning side effects, authentication requirements, file size/type constraints, or whether the upload is permanent. This is insufficient for a tool with no annotation support.

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 a single sentence in Chinese that conveys the action and the result efficiently. It is front-loaded with the verb and resource, and every word adds value. There is no redundant or irrelevant information.

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?

Though the tool is simple, the description is too brief to be complete. It lacks details about the 'path' parameter, input requirements, and any behavioral constraints. With no annotations and an output schema present, the description should provide more context, but it only covers the basic function.

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 one parameter 'path' with no description, and the schema description coverage is 0%. The description does not explain what 'path' means (e.g., local path, URL, base64), nor how it relates to the upload action. With low schema coverage, the description was expected to compensate, but it fails to provide any parameter semantics.

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 tool uploads an image to Xianyu CDN and returns the image URL plus dimensions. The verb '上传' (upload) is specific, the resource '图片到闲鱼 CDN' is precise, and the outcome is mentioned. This distinguishes it from sibling tools, none of which handle media uploads.

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 implies usage for uploading images but provides no explicit guidance on when to use this tool versus alternatives. Since there is no competing upload tool among siblings, the context is clear enough, but the description does not state any exclusions or prerequisites.

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