Hot reload

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

No annotations provide safety hints (readOnly, destructive). Description does not disclose side effects (e.g., loss of unsaved state, reset of script variables). More behavioral context is needed for a mutation tool.

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?

Two concise sentences, front-loaded with main purpose, every sentence adds value.

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?

Tool is simple with few params; description covers core functionality. Omission of response_format or game_id is acceptable as schema describes them. Slight improvement could mention usage in active game.

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 covers all 4 parameters with descriptions (100% coverage). Description loosely restates scripts and reload_scene parameters but adds no new insight beyond 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?

Description clearly states the tool reloads GDScript files and/or scene without restarting, specifying the verb and resource. It distinguishes from siblings like add_node, game_change_scene by focusing on hot reloading.

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?

Description conveys when to use (to reload scripts/scene without restart). It does not explicitly exclude alternatives or state when not to use, but the context implies appropriate usage.

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