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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds one useful behavioral fact — the world must be 'owned' — implying an ownership/auth constraint. Beyond that it adds no failure modes, return format, or pagination detail.

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 tight sentences with zero filler; the core action is front-loaded and the routing advice follows. Every clause 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?

Annotations cover the safety profile, the lone parameter is fully described in schema, and the description names the alternative tools for related needs. The only gap is that return content ('summary and media') is not elaborated, though no output schema exists to compensate.

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 100% for the single world_id parameter, and the schema itself documents that it comes from list_worlds. The description adds no additional parameter meaning, so the baseline of 3 applies.

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?

States a specific verb and resource: 'Read an owned world's summary and media.' It explicitly names the sibling tools that cover adjacent needs (list_world_assets, list_creator_flow_projects), helping distinguish it. However, 'summary and media' is loose about exact return content and it doesn't differentiate itself from get_world_asset.

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?

It routes the agent to the right alternatives for adjacent tasks ('Use list_world_assets to inspect its library and list_creator_flow_projects for project discovery'), which implies when this tool is the wrong choice. It stops short of stating an explicit when-to-use condition or any prerequisites for this tool itself.

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