Build (import resources)

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

Description discloses that the tool compiles scripts, generates the .godot cache, and surfaces errors, which is transparent given no annotations. Could be more explicit about side effects like cache overwrite.

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-load the main action and purpose with no extraneous words.

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 build tool with 3 optional parameters and no output schema, the description covers purpose, outcome, and error surfacing adequately.

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 is 100% with clear parameter descriptions; description does not add parameter-specific meaning, but baseline 3 is appropriate.

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 'Import/reimport the project headlessly, compiling scripts and generating the .godot cache' and calls it the 'equivalent of a compile check,' distinguishing it from sibling tools like godot_run (run) or godot_export (export).

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 usage for error checking without running, but does not explicitly mention when not to use or point to alternatives like godot_validate_script or godot_run.

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