vrchat_group_post_create

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

The description adds a meaningful behavioral detail: 'Does not notify members unless sendNotification is true,' which is not captured by the sparse annotations (only readOnlyHint: false). However, it does not disclose other potential behaviors such as permission requirements, side effects beyond notification, or error conditions.

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, front-loaded sentence that immediately identifies the action and includes one crucial behavioral caveat. Every word earns its place; there is no redundant or explanatory fluff.

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?

Given the tool's complexity (8 parameters, 3 required) and the rich schema descriptions, the description adds the key notification nuance but omits other context such as group membership prerequisites or potential failure modes. The output schema helps, but the description itself is minimal and leaves some operational context unstated.

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 schema already provides 100% coverage for all 8 parameters with descriptive text, so the baseline is 3. The description reinforces the sendNotification parameter ('Does not notify members unless sendNotification is true') but does not add new semantic information 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 states a specific action ('Create a group post') and resource ('group post'), with an explicit parenthetical ('announcement') that clarifies the post type. This clearly distinguishes the tool from sibling tools like vrchat_group_post_update and vrchat_group_post_delete.

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?

No explicit guidance is provided about when to use this tool versus alternatives, nor are any prerequisites or exclusions mentioned. The only hint is the verb 'Create,' which implies usage but does not offer the contextual guidance that would help an agent choose this over update/delete or other group-related tools.

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