godot-mcp-pilot

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

With no annotations provided, the description carries full burden but only states it's a read operation. It doesn't disclose behavioral aspects like what happens if the project path is invalid, whether it returns structured data or raw text, error conditions, or performance characteristics. The description is minimal beyond stating the basic operation.

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 perfectly concise with two sentences that each earn their place. The first sentence states the core purpose, the second explains the optional filtering capability with helpful examples. No wasted words or redundant information.

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 read-only tool with 2 parameters and 100% schema coverage, the description is adequate but minimal. Without annotations or output schema, it should ideally provide more context about return format, error handling, or typical use cases. The description meets minimum requirements but leaves gaps in behavioral understanding.

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 fully documents both parameters. The description adds marginal value by providing concrete examples of section values ('application', 'display', 'input', etc.), but doesn't explain parameter interactions or provide additional semantic context beyond what's in 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 states the verb ('Read') and resource ('project.godot configuration'), specifying the exact file being accessed. It distinguishes from sibling tools like 'get_project_info' by focusing on configuration settings rather than general project metadata.

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 the optional section parameter, listing example sections like 'application' and 'display'. However, it doesn't explicitly state when NOT to use this tool versus alternatives like 'get_project_info' or 'set_project_setting'.

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