editor_static_model_details

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

readOnlyHint=true already tells the agent this is a safe read. The description adds the useful qualifier 'live' (runtime actor state, not just the asset reference) and that it covers both the model reference and actor details, but says nothing about failure behavior when the actorId is invalid or not loaded.

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 with no filler. The resource type and the two returned artifacts are stated immediately, so nothing needs to be trimmed.

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?

An output schema exists, so return values need not be explained, and the tool is a simple one-param read with full schema coverage. The only remaining gap is not positioning it relative to editor_actor_details, but for a read-only detail lookup the description is essentially sufficient.

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% and the actorId property already documents its origin ('StaticModel actor GUID from editor_scene_graph'), so the schema carries parameter semantics. The description adds no further detail on the identifier or on what happens with a non-StaticModel actor, making baseline 3 appropriate.

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?

Specific verb ('returns') plus a precise resource ('assigned model reference and live actor details for a loaded StaticModel actor'). It is clearly distinguishable from editor_set_static_model (which mutates) but doesn't explicitly contrast itself with the adjacent editor_actor_details, which plausibly covers overlapping ground.

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?

Usage is only implied by the phrase 'loaded StaticModel actor' — the agent must infer it applies after a StaticModel exists in the scene. No explicit when-to-use, no exclusion against editor_actor_details or editor_scene_graph, and no note that the actor must be loaded before calling.

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