vrcx_user_relationship_sessions

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

Annotations already provide readOnlyHint=true. Description adds that results are 'from VRCX logs' and 'limited by default', which gives extra context about data source and default behavior but lacks details on pagination or default limit value.

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?

Two sentences with clear front-loading of purpose and immediate usage guidance. No redundant or irrelevant information.

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?

Covers purpose, read-only nature, data source, and default limit behavior. Lacks clarification on how to specify the target user (userId vs displayName) and ordering of results. Existence of output schema reduces need to explain return values.

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 description must compensate. Only mentions 'limited by default' hinting at limit parameter, but doesn't explain userId or displayName beyond their names. Parameter names are somewhat intuitive, but the description adds minimal meaning.

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?

Clearly states 'list recent shared instance sessions with a user from VRCX logs', which is a specific verb+resource. Differentiates from siblings by specifying 'deep history' and 'read-only', contrasting with related tools like vrcx_user_relationship_summary.

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?

Explicitly says 'Use this for deep history', implying it's for detailed logs rather than summaries. Does not mention exclusions or alternative tools, but the context of siblings provides implicit guidance.

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