vrchat_friends_search

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

The description adds the key detail that the search is by 'display name' (not username or ID), and reinforces the read-only nature already indicated by annotations. This goes beyond annotations alone.

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 extremely concise (5 words) with no wasted text. However, the brevity sacrifices completeness; a slightly longer description could improve utility without harming 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?

Given the presence of an output schema (reducing need to describe returns) and annotations, the description is adequate but not thorough. It fails to explain pagination or effect of optional parameters, leaving gaps.

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 should explain all parameters. It only indirectly covers the 'query' parameter via 'search by display name', but provides no meaning for 'maxResults' or 'includeOffline'. Incomplete compensation.

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 'search', resource 'friends', and criterion 'by display name'. It distinguishes from sibling tools like vrchat_friends_list (which likely lists all friends) and vrchat_friend_details (which shows details for a specific friend).

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 implies usage for finding specific friends by name, but does not explicitly state when to use this tool over alternatives like vrchat_friends_list or vrchat_friends_overview. No exclusions or prerequisites are provided.

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