vrchat_me

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

Annotations already declare readOnlyHint=true. The description adds that groups can be included as a paged list, which is useful behavioral context beyond the annotation. No contradiction and no missing safety info.

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 sentences: first states purpose, second gives usage guidance. No wasted words, front-loaded with the core action. Perfectly concise.

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 complexity (8 optional params, output schema present), the description covers the primary use cases (view presets, custom fields, group pagination). Minor parameters like 'compact' are omitted, but the overall picture is clear. Acceptable completeness.

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 0%, so the description must compensate. It explains the 'view' enum, 'fields' array, and group pagination parameters. However, 'compact' and 'maxArrayLength' are not mentioned, leaving a gap. Overall, it adds moderate value over the raw schema.

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 'Get your profile (read-only)', which is a specific verb+resource. It distinguishes from sibling 'vrchat_user_profile' (another user's profile) and 'vrchat_profile_update' (write). The mention of view presets further clarifies functionality.

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 gives clear context (use view presets, override fields, include groups) but does not explicitly state when not to use this tool or name alternatives. The name and context imply it is for own profile, leaving minimal ambiguity.

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