editor

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

Description lists actions and their effects (open editor, check if running). Annotations indicate idempotentHint=true, which aligns with status being idempotent; no contradictions. Could mention potential side effects of launch but annotations already cover.

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?

Extremely concise, using a bullet list for actions. Every sentence adds value without redundancy.

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?

Lacks output schema, description does not hint at return values or error conditions. For a tool with two actions, more behavioral detail (e.g., what status returns) would improve completeness.

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 has 100% coverage of parameters with descriptions. Description repeats enum values and optional nature, adding no new semantic detail beyond what the schema provides.

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 it controls the Godot editor, lists actions (launch, status) with optional params, and distinguishes from sibling tool 'project' for running games.

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?

Explicitly tells when to use 'project(action="run")' instead, and clarifies required vs optional parameters in a structured list.

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