get-current-scene

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

With no annotations, the description implicitly suggests a read-only operation but does not explicitly state it is non-destructive or require permissions. The behavioral traits are somewhat transparent for a getter, but could be more explicit about side effects or prerequisites.

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 short sentence with no redundant words. It is concise and front-loaded with the core purpose. However, it could be slightly more structured by separating the main purpose from the included elements.

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 is simple with two optional boolean parameters and no output schema, the description is fairly complete. It covers what the tool does and what is included, though it omits specifics about the returned format or potential limitations.

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% with both parameters described. The description does not add extra meaning beyond the schema; it mentions 'tokens' and 'layout' which align with includeTokens but does not elaborate on includeHidden. Baseline 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 clearly states the tool retrieves information about the currently active scene, specifying it includes tokens and layout. It distinguishes from sibling tools like 'list-scenes' (lists all) and 'update-scene' (modifies), providing a specific verb and resource.

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. For example, it doesn't mention that to get a specific scene by ID, one might use another tool, or that this tool is only for the active scene. The description lacks usage context.

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