vrchat_auth_begin

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

Discloses side effect of opening a browser UI, matching readOnlyHint=false. No contradiction. Could mention that user interaction is required, but acceptable for a simple tool.

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 sentence, no unnecessary words, front-loaded with core action. Perfect conciseness.

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?

Tool has no parameters and an output schema exists (not shown), so description need not detail returns. It sufficiently covers the initiation aspect but could mention prerequisites like needing to be logged out.

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?

No parameters exist, and schema coverage is 100%. Description adds no parameter info, but baseline is 3 per guidelines for high coverage.

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?

Description clearly states the action ('begin login flow') and method ('via local browser UI'). Distinguishes from siblings like vrchat_auth_status and vrchat_auth_logout by implying this is the initiation step.

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?

Implied usage as the first authentication step, but no explicit when-to-use or alternatives (e.g., use vrchat_auth_status to check if already authenticated). No guidance on when not to use.

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