get_remote_tree

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

Discloses return format {tree, node_count, truncated?}, collapse behavior, and default values beyond annotations (readOnlyHint, destructiveHint). No contradiction.

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 paragraph, front-loaded with main purpose, then scoping and parameters. Efficient but could be slightly more structured; still well above average.

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?

Covers all parameters, scoping, return structure, and collapse feature. No output schema but provides sufficient detail for correct invocation.

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?

Description fully explains all five parameters with defaults and meaning despite 0% schema coverage. Path as subtree root, depth levels, max_nodes, max_children, collapse behavior all detailed.

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?

Explicitly states 'Dump the live scene tree of the RUNNING game' and distinguishes from sibling get_scene_tree as 'runtime counterpart'. Clear verb and resource with differentiation.

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?

Provides clear scoping advice ('SCOPE IT to stay under token limits') and explains parameter usage for controlling output size. Does not explicitly mention when not to use, but implicitly against sibling.

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