vrchat_gallery_image_upload

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

The annotation only says readOnlyHint=false, so the description correctly conveys a write operation to the signed-in account's gallery. It adds useful context by stating the image is not attached to group posts or events. However, it does not disclose potential side effects such as replacing existing gallery items, rate limits, or upload failure behavior, though the output schema may cover some of this.

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 two tightly written sentences. The primary action is stated first, and the differentiation from group-post/event attachment follows immediately. There is no filler or redundant material.

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?

For a single-parameter upload tool with a detailed input schema and an output schema, the description is sufficient: it identifies the target, the accepted input class, and a key non-goal. An agent has everything needed to select and invoke the tool correctly.

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 already provides 100% coverage for the single parameter imagePath, including path constraints, file type, dimensions, and size limit. The description's mention of 'validated static PNG' aligns with the schema but adds no new parameter-level meaning beyond what the schema already states.

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 uses a specific verb ('Upload') and resource ('signed-in VRChat account gallery'), and narrows the payload to 'a validated static PNG.' The explicit disclaimer that it 'does not attach the image to a group post or event' distinguishes it from sibling tools like vrchat_group_post_create or vrchat_event_create.

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 makes the primary use case clear: uploading an image to the account gallery. The sentence 'This does not attach the image to a group post or event' provides an explicit exclusion that helps an agent choose this tool over attachment-related siblings, though it does not name those alternatives directly.

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