imgui_list_scenes

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

No annotations are provided, so the description carries the full disclosure burden. As a read/list operation, there's little risk to disclose, and the description accurately reflects safe behavior. It doesn't discuss output format or whether the 'active scene' is a separate field, but the low-risk nature keeps this adequate.

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?

The description is a single sentence that efficiently conveys the tool's purpose. It's appropriately sized for a zero-parameter listing tool with no additional complexity to document.

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 simple listing tool with no parameters, no output schema, and clear purpose, the description is reasonably complete. It tells the agent what data it will receive (scenes, window lists, active scene). It could mention whether the output is relevant to debugging or inspection workflows, but this is a minor gap.

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?

With 0 parameters and 100% schema coverage, the parameter dimension is trivially satisfied. The baseline of 4 for zero-param tools applies here since there's nothing to explain beyond what the schema declares.

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 clearly states the verb ('List') and resource (scenes, window lists, active scene). It's specific enough to distinguish from siblings like imgui_list_snapshots, imgui_list_fonts, and imgui_get_state, though it doesn't explicitly differentiate from these alternatives.

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?

The description implies it's for inspection/listing purposes (when you want to see current scene state), which naturally contrasts with mutation tools. However, it doesn't explicitly state when to use this vs imgui_get_state or other inspection tools, nor does it mention any prerequisites.

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