get_scene_dependencies

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

No annotations provided. Description only states what it returns, not how it behaves (e.g., recursive? requires open scene?). Lacks details on side effects or edge cases.

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?

Single sentence, no waste. Front-loaded with action and resource. Every word serves a purpose.

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 low complexity (1 param, no output schema), description is adequate but incomplete: does not specify return format, recursion depth, or file format requirements.

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 100% with parameter 'path' described as 'Scene file path'. Description adds no additional meaning beyond schema, so baseline score.

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?

Description clearly states verb 'Get', resource 'scene file', and specifics 'dependencies (scripts, resources, sub-scenes)'. Distinguishes from sibling tools like get_resource_dependencies which cover broader resources.

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?

Implies usage when needing scene-specific dependencies, but no explicit guidance on when to use vs alternatives (e.g., find_node_references, get_resource_dependencies). Does not mention prerequisites or exclusions.

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