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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the description is free to add value elsewhere — and it does, clarifying that nothing is generated on demand and that results are pre-published assets with captions. Returned content types are described, though nothing is said about volume, pagination, or what happens for a world with no pictures.

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, front-loaded with the resource and content inventory, followed by the usage cue. The middle clause is a slightly dense list but every element carries information; nothing is wasted.

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 only two parameters, full schema coverage, and rich annotations, the description supplies what structured data cannot: what the pictures are, that they are captioned, and that no rendering occurs. Only edge-case behavior (empty results, unsupported world) is left unstated, which is tolerable for a simple read 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 coverage is 100% and the world enum is spelled out in the schema itself, so the description only echoes 'for a world or a place' without adding format or selection guidance. Baseline 3 is appropriate when the schema does the heavy lifting.

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 ('Return pictures already published on orbitstudio3d.com'), enumerated content types (printed-model photos, app renders, map texture), and explicitly disambiguates from the misleading name by saying 'Nothing is rendered on request.' An agent cannot confuse this with a rendering or model-suggestion 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?

Gives a clear triggering condition ('Use it when the user wants to see what a model looks like') plus an explicit exclusion ('Nothing is rendered on request'). No sibling is named as an alternative, but none of the listed siblings (list_worlds, search_places, suggest_model) is a plausible substitute, so the gap is minor.

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