get_project_structure

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

With no annotations provided, the description carries the full burden. It hints at traversal behavior via maxDepth (default 3, recommended 5-10) but does not disclose return format, performance implications, or whether the hierarchy includes hidden objects. The read-only nature is implied by 'Get'.

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 two sentences long and front-loaded with the purpose. The IMPORTANT note about maxDepth is concise and actionable, earning its place without redundancy.

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 has 3 parameters and no output schema, so the description should compensate by explaining what the hierarchy looks like. It does not mention the return structure or edge cases, and lacks guidance on when to choose this tool over siblings. However, the maxDepth guidance adds useful context, making it minimally complete.

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 baseline is 3. The description reinforces the maxDepth recommendation already present in the schema but does not add substantial new meaning for path or scriptsOnly parameters, nor does it clarify their behavior beyond the schema.

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 tool as retrieving the game hierarchy, which is distinct from file tree or place info tools. However, the word 'complete' is slightly misleading given the maxDepth default of 3, and it does not differentiate from sibling tools like get_descendants.

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 provides parameter guidance for maxDepth but does not explain when to use this tool versus alternatives like get_descendants or get_instance_children. No explicit context or exclusions are given for tool selection.

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