upload_prop_sheet

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

With no annotations provided, the description carries the burden of behavioral disclosure. It does state the core behaviors: automatic upload and registration. However, it does not disclose side effects such as overwriting an existing prop sheet, whether the prop must already exist, or what response is returned after upload.

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 extremely concise, two short sentences. The primary purpose is front-loaded, and '自动上传+登记' summarizes the behavior. '免费' is an extra business detail but does not make the description bloated. Every key element 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?

This is a simple 2-parameter tool with no output schema and no annotations, so the description only needs to cover selection and basic invocation. The current description covers the client-image use case and upload/register behavior, but it omits practical invocation details like whether prop_id must reference an existing prop and whether an existing prop sheet is replaced. This is a clear but not severe gap.

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 50%, with file_path already documented as '本地道具图路径' while prop_id has no schema description. The description adds the idea that the image is a client-provided prop setting image, which helps interpret file_path, but it does nothing to explain prop_id or how to obtain it. The description does not compensate enough for the uncovered parameter.

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 states a specific verb and resource: using the client's own image as a prop's setting image, then automatically uploading and registering it. It distinguishes itself from sibling generate_prop_sheet by emphasizing '客户自有图片' rather than generated content, so an agent can tell them apart.

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 phrase '用客户自有图片' provides clear context for when to use this tool: when the client provides their own image for a prop sheet. It does not explicitly name exclusions or alternatives like generate_prop_sheet, but the use case is clear enough to guide selection.

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