vrchat_search_avatars

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It adds some useful context about search limitations (own/featured avatars only) and user permissions, but doesn't describe important behavioral aspects like pagination behavior (offset parameter), rate limits, authentication requirements, or what the response format looks like.

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 appropriately sized with three clear sentences. The first sentence states the purpose, the second and third provide important usage constraints. There's no wasted text, though it could be slightly more structured with bullet points for the constraints.

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 complexity (13 parameters, no schema descriptions, no output schema, no annotations), the description is incomplete. It covers basic purpose and some usage constraints but doesn't address parameter meanings, return values, error conditions, or important behavioral aspects needed for a search tool with many filtering options.

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 and 13 parameters, the description provides no information about any parameters. It mentions 'query filters' generically but doesn't explain what specific filters are available, their purposes, or how they interact. The description fails to compensate for the complete lack of parameter documentation in the 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 clearly states the tool's purpose as 'Search and list avatars by query filters', which is a specific verb+resource combination. However, it doesn't explicitly differentiate this tool from sibling tools like 'vrchat_search_groups' or 'vrchat_search_worlds' beyond the resource type, missing full sibling differentiation.

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 provides clear context about when to use this tool: 'You can only search your own or featured avatars. It is not possible as a normal user to search other people's avatars.' This gives important usage boundaries but doesn't explicitly mention when to choose this tool over alternatives like 'vrchat_select_avatar' or other search tools.

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