set_scene_meta

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states that metadata is set, without mentioning whether it overwrites existing keys, merges, or requires specific permissions. The lack of details on side effects or idempotency leaves the agent uncertain about the tool's behavior.

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 of 9 words, which is concise and front-loaded. However, it could include a brief note about overwrite behavior or return value without becoming verbose, earning a slightly lower score than the highest tier.

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?

The tool is relatively simple with a complete schema, but the description lacks behavioral details (e.g., overwrite behavior, return value). Given the absence of an output schema and annotations, the description should provide more context to be fully complete, but it is minimally adequate.

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%, so the input schema already documents each parameter's purpose and constraints. The description adds no additional meaning beyond the schema, meeting the baseline expectation but not exceeding it.

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 'Set metadata on the current scene's root node' uses a specific verb ('Set') and clearly identifies the resource ('metadata on the current scene's root node'). It distinguishes from related tools like get_scene_meta (retrieval) and set_game_node_property (which sets game node properties, not scene metadata).

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 and input schema note that scene_path should be omitted because only the current scene is supported, providing clear context for when to use this tool. However, it does not explicitly contrast with alternatives like cross_scene_set_property or set_game_node_property, which could help an AI agent decide between them.

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