get_scene_transition_override

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

No annotations are provided, so the description must carry the behavioral burden. It discloses that the tool retrieves an override 'if any,' implying a possible null/absent result, but it does not describe the return structure or any side effects. For a simple getter this is adequate but not rich.

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 exceptionally concise and front-loaded, with the primary purpose in the first sentence and a minimal Args section. Every sentence serves a functional purpose, though the Args line duplicates schema 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?

For a one-parameter getter, the description is mostly sufficient, but it does not define what a 'transition override' is or describe the return value's structure or type. Given no output schema, the description should clarify what the caller receives, especially the 'if any' case.

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% schema description coverage, the description must add meaning beyond the schema. It merely restates 'scene_name: Name of the scene,' which adds little beyond the schema's existing title 'Scene Name.' No format, constraints, or clarifications are provided.

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 identifies the action ('Get') and the resource ('transition overridden for a specific scene'), making it distinguishable from related tools like get_current_scene_transition. The phrase 'if any' adds nuance about the optional nature of the override.

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 when to use the tool: when you need to know the transition override for a particular scene. However, it does not explicitly mention alternatives or exclusions, such as when to use get_current_scene_transition instead, leaving usage guidance implicit.

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