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

Goes well beyond the readOnly/idempotent annotations by disclosing pagination behavior (50 items per response, up to 600 items, use itemTotal for real length and nextOffset to page), the requirement to exhaust pages, and the scope fact that all layer types including Studio-only ones are readable here.

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?

Front-loads the return shape before the pagination caveat, and every sentence carries information the agent needs (id provenance, page size, total count, page-exhaustion rule, readable scope). No filler.

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 carries the full burden and does so: it describes the returned fields, the playlist item structure, truncation semantics, and the pagination contract needed to retrieve a full playlist correctly.

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%, so baseline is 3; the description adds meaning by tying offset to the 50-item page size and the nextOffset field, plus reinforcing where layerId and projectId originate. That is a genuine increment over the schema's own parameter descriptions.

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 one layer in full') and immediately enumerates what is returned: type, name, position, settings, and playlist items plus which is playing. This is clearly distinguishable from siblings like livereacting_add_layer, livereacting_set_playlist, and livereacting_get_scenes.

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?

Points the agent at the prerequisite source of ids ('Layer ids come from livereacting_get_scenes') and gives operational guidance to read every page before judging playlist contents. It does not explicitly state when NOT to use this tool versus alternatives such as get_scenes, but the context is clear.

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