vrcx_memos_world_get

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

The readOnlyHint annotation already covers the safety profile, and the description merely restates 'read-only' without adding behavioral context beyond it. It discloses nothing about behavior for a missing memo (e.g., null return vs error) or any side effects, so the description adds no value beyond the annotation.

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?

A single front-loaded sentence of seven words that delivers the verb, resource, and key. Every word earns its place with no filler or repetition.

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?

The tool is low-complexity (one required parameter, no nested objects), an output schema exists so return values need not be explained, and the readOnlyHint annotation covers safety. The only notable gaps are the unaddressed missing-memo behavior and the lack of explicit distinction from sibling memo getters, both minor for this simple tool.

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 the description carries the burden of explaining the parameter. It only repeats 'by worldId', which is nearly identical to the property name itself; it does not explain the expected format of a worldId, where to obtain it, or what constitutes a valid value. Minimal added meaning over 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 states a specific verb ('Get'), a specific resource ('VRCX world memo'), and the lookup key ('by worldId'), making the core function clear. It does not explicitly contrast with the sibling tools vrcx_memos_user_get and vrcx_memos_avatar_get, though the 'world' qualifier alongside the name conveys the entity scope.

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?

There is no guidance on when to use this tool versus the analogous sibling tools vrcx_memos_user_get or vrcx_memos_avatar_get, and no mention of prerequisites or context. The appropriate usage (when you have a worldId and need its memo) is only implied, not stated.

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