vrchat_group_profile

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

Annotations already declare readOnlyHint=true, and the description redundantly states 'read-only', which is consistent. However, the description does not add other behavioral context like authentication requirements, rate limits, or caching behavior. Given that the annotations cover the primary safety trait, a score of 3 is appropriate.

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 a single sentence with no unnecessary words. It is front-loaded with the verb and resource, making it easy to scan. Every word earns its place.

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?

An output schema exists, so return values are not needed. However, with 5 parameters and no description beyond two identifiers, the tool is incomplete for an agent to use without additional context. The description covers core purpose but lacks parameter semantics.

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%, yet the description only mentions groupId and shortCode. It fails to explain the purpose of 'fields', 'compact', and 'maxArrayLength'. With no parameter details, the agent cannot correctly invoke the tool, especially for optional filtering or formatting.

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 'Get', the resource 'group profile', and the two identifier methods (groupId or shortCode). It distinguishes this as a single-profile fetch tool among multiple group-related siblings, though it could be more explicit about when to use this vs. group search or membership tools.

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 you need either groupId or shortCode, but it does not provide explicit guidance on when to use this tool over alternatives, such as vrchat_groups_search for listing groups. There is no mention of prerequisites or exclusions.

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