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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, not open-world). The description adds genuinely new behavioral context in 'Returns public card metadata only', which bounds what the agent will get back. The trailing 'Never invent avatar IDs or simulate their players' is more an anti-hallucination instruction than a disclosed trait, and no pagination or scoping behavior is described.

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?

Three short sentences, front-loaded with the action and return scope. Slightly diluted by the second and third sentences mixing design advice and anti-hallucination warnings, but overall tight with no padding.

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?

With no output schema, the description does well to state 'public card metadata only', but it leaves the two required input parameters and their semantics unexplained at 0% schema coverage. For a tool requiring both workspaceId and worldId, an agent lacks enough to call it confidently in edge cases.

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% and neither parameter is documented in the schema, so the description carries the full burden. It only obliquely implies workspace scoping via 'workspace avatars' and never explains worldId or how the two IDs relate, leaving an agent to guess the required identifiers.

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 read operation over a specific resource class ('real workspace avatars, games, apps and Worldstreams') and names what it returns (catalog IDs, readiness, attachment state). It is distinguishable from siblings like list_world_experiences and get_world_experience, though the head verb 'Read' is weaker than 'List'/'Get' for a listing tool.

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?

'Use existing built experiences before designing their pages' gives one contextual trigger for invoking the tool. It does not name alternatives (e.g. list_world_experiences vs get_world_experience) or state any when-not-to-use condition, so guidance remains implied rather than explicit.

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