godot-mcp-pilot

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

With no annotations provided, the description carries the full burden. It discloses key behavioral traits: it writes/mutates data ('Write a setting'), creates sections if missing, and specifies value formatting requirements. However, it doesn't mention permission requirements, error conditions, or what happens on success/failure.

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?

Three sentences with zero waste. The first states the core purpose, the second specifies value formatting rules, and the third reveals important behavioral detail (creates sections). Every sentence earns its place and information is front-loaded appropriately.

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 mutation tool with no annotations and no output schema, the description provides adequate but incomplete coverage. It explains the core operation and value formatting, but lacks information about return values, error handling, and permission requirements that would be helpful for an agent invoking this tool.

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 schema already documents all four parameters thoroughly. The description adds value by explaining the 'value' parameter's formatting requirements with examples, but doesn't provide additional semantic context for the other parameters beyond what the schema offers.

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 states the specific action ('Write a setting to project.godot') and identifies the resource (Godot project configuration file). It distinguishes from sibling tools like 'get_project_settings' (read) and 'update_project_uids' (different operation) by focusing on writing configuration values.

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 clear context for when to use this tool (writing Godot config values with specific formatting requirements). It doesn't explicitly mention when NOT to use it or name alternatives, but the context is sufficiently clear given the sibling tools available.

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