Current scene

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, covering the safety profile. The description adds useful behavioral context beyond annotations by explaining that hidden tokens are omitted unless includeHidden is set and that tokens are only listed when includeTokens is true.

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 that conveys the tool's purpose, scope, and parameter-sensitive behavior without repetition or filler. Every clause adds relevant information.

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 burden of explaining return content, and it does so by listing the scene data fields (size, background, navigation, walls, lights, sounds, notes, tokens). It could be slightly more explicit about the output format, but for a read-only, parameter-free-required tool, this is sufficiently complete.

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?

The schema fully describes both parameters (includeHidden and includeTokens) with defaults and explanations, so the baseline is 3. The description lightly reinforces these parameters but does not add meaningfully new semantic detail beyond the schema.

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 uses a specific verb ('Describe') and names a clear resource: the currently active scene. It also enumerates exactly what is included (size, background, navigation, counts, notes, tokens), making the purpose unmistakable and distinct from sibling tools like list-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?

'The scene that is active for everyone' clearly signals when this tool is appropriate: when you need details of the current shared scene. It does not explicitly mention alternatives or exclusions, but the context is strong enough that an agent can infer when to invoke it.

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