Godot MCP Meta Manager

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

The description lists the actions (server_info, doctor, tool_help, codex_profile), which adds context beyond the annotations (readOnlyHint, idempotentHint). It does not contradict annotations and clearly indicates a safe, read-only, idempotent 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?

The description is a single sentence that front-loads key information. It is concise, contains no filler, and effectively communicates the tool's purpose.

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 that an output schema exists and annotations cover safety, the description is sufficient for a meta tool. It lists actions and hints at usage, though it could briefly explain when to use each action.

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 has 100% coverage with descriptions for all 4 parameters. The description lists the action enum values but does not add significant meaning beyond what the schema provides. 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?

The description explicitly lists the tool's capabilities (server info, doctor checks, tool help, codex profile) and distinguishes it from sibling tools by stating 'Start here.' This makes it clear that it's a meta-information tool, not for domain-specific 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 phrase 'Start here' implies it is the initial tool to use, but it does not specify when to avoid it or provide alternatives. While the context suggests it is for meta queries, no explicit usage guidance or exclusions are given.

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