vrchat_friends_overview

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

Annotations already declare readOnlyHint=true, and the description reinforces read-only behavior. It adds 'enriched world/group info' but does not disclose other behavioral details like pagination or rate limits. The description is adequate but not exceptional beyond annotations.

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 one sentence of 11 words, extremely concise. However, it could benefit from a slightly more structured format to improve readability.

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 6 parameters and no parameter documentation in the schema or description, the tool is incomplete. The existence of an output schema mitigates the need to explain return values, but parameter usage remains underspecified.

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?

With 0% schema description coverage, the description must compensate but only vaguely mentions 'status and location'. None of the 6 parameters are explained, leaving the agent without semantic guidance for parameters like statusFilter, includeOffline, instanceDetailLevel, etc.

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 clearly states the verb 'Summarize', the resource 'friends', and the criteria 'by status and location'. It distinguishes itself from siblings like vrchat_friends_list, vrchat_friends_search, and vrchat_friend_details by emphasizing summarization and enriched info.

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 guidance is provided on when to use this tool versus alternatives. With many sibling tools, the agent receives no context for appropriate invocation.

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