project

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

Annotations are minimal (readOnlyHint=false, destructiveHint=false, etc.), but the description does not elaborate on side effects, error conditions, or behavioral details. For example, it doesn't explain if 'run' blocks, what 'stop' does if no game is running, or whether 'settings_set' overrides or appends.

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 concise and front-loaded with 'Godot project operations.' It uses bullet points for actions, which is readable. However, the structure could be improved by separating action descriptions from parameter lists more clearly (e.g., using tables).

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 the tool's complexity (7 actions, 7 parameters, no output schema), the description covers all actions and parameter dependencies. However, it lacks information about return values (e.g., what does 'version' return? 'settings_get'?) and does not specify how outputs are structured.

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?

The schema covers all parameters with descriptions (100% coverage), so baseline is 3. The description adds value by grouping parameters per action (e.g., 'run (-> scene_path, project_path)') and indicating required vs optional dependencies, improving clarity beyond the flat 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 explicitly lists seven distinct actions (info, version, run, stop, settings_get, settings_set, export) for Godot project operations, making the tool's purpose clear. It differentiates from sibling tools (e.g., animation, audio) by focusing on project-level tasks.

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 when to use this tool (for project operations) through its multi-action listing, but does not provide explicit guidance on when not to use it or compare with alternatives. No 'when-to-use' or 'alternatives' mention.

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