scene

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

With no annotations provided, the description must disclose behavioral traits, but it only says 'manages scenes for later recall'. It does not mention side effects like changing the current view when recalling, deleting scenes irreversibly, or storing state. This is a significant gap for a mutation-capable tool.

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 with no fluff or redundant information. It is front-loaded with the core purpose, though it could be slightly more informative without adding bulk.

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?

Given the tool has multiple actions (store, recall, clear, etc.) and no annotations, the description is too sparse. It does not cover when to use each action, potential side effects, or how scenes interact with the view, leaving the agent with an incomplete picture. The output schema exists but does not compensate for the lack of behavioral context.

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 schema provides meaningful descriptions for both 'key' and 'action', including examples and allowed values. The tool description adds no additional parameter semantics, so the baseline of 3 is 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?

The description states it manages scenes for later recall, identifying the resource (scenes) and a general purpose, but 'manages' is vague and doesn't specify the range of actions (store, recall, clear, etc.) that the schema reveals. It also doesn't differentiate this tool from the sibling 'scene_order', which also relates to 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?

No guidance is provided on when to use this tool versus alternatives such as 'scene_order', 'create', or 'delete'. The description only gives a general purpose without any context on conditions, prerequisites, or exclusions.

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