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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful content context — that each experiment has a live demo and spans WebGL, shaders, AR, and courses — but says nothing about result count, ordering, or whether demos are external links. No contradiction with annotations.

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?

One compact sentence, front-loaded with the resource name, with no wasted words. It reads slightly like marketing copy ('push interactive 3D') rather than operational instruction, but the structure is efficient.

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?

For a one-parameter, read-only list tool with no output schema, the description covers what the collection contains but not what a caller receives (fields, count, pagination) or how it differs from the sibling getter. Adequate but with clear gaps.

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 'lang' enum parameter, which already explains the 'en'/'es' values and the instruction to use the user's language. The description adds nothing about language handling, so the baseline 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?

The description explains what Hilo Studio's Lab experiments are (WebGL, shaders, AR demos) but never states the verb the tool actually performs — it never says it returns a list of experiments. The name and title carry that meaning; the description itself is descriptive of the domain rather than the operation, and it does not distinguish itself from the sibling hilo_get_lab_experiment.

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?

No guidance on when to call this versus hilo_get_lab_experiment (single experiment) or hilo_find_relevant_work. There is no mention of prerequisites, expected context, or exclusions. The agent must infer usage entirely from the name.

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