vrchat_world_profile

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

Read-only behavior matches annotation. Adds identifier options but no further behavioral details (e.g., error handling, permissions). With annotation present, description provides minimal extra value.

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 short sentence, front-loaded. Concise but lacks detail on parameters, earning a minor deduction due to incompleteness.

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?

Despite output schema and annotation, description fails to contextualize 3 of 5 parameters. Incomplete for a tool with multiple optional parameters.

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 is 0%, description only hints at two parameters (worldId, name) out of five. Does not explain fields, compact, or maxArrayLength, leaving gaps for effective use.

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?

Clearly states it gets a world profile by worldId or name. The verb 'Get' and resource 'world profile' are specific, distinguishing it from search or list siblings.

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?

Implies usage when you have worldId or name. No explicit when-not or alternatives, but the context is clear for this simple retrieval tool.

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