editor

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

Annotations (idempotentHint=true, destructiveHint=false, readOnlyHint=false) provide safety profile. Description adds basic behavior (launch opens editor, status checks running) but no details on side effects or state changes.

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?

Brief three-sentence description with clear structure: overall purpose, action list, alternative hint. No filler words.

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 simple tool with two actions and full schema coverage, description covers purpose, usage, and key alternative. Lacks details on return values (e.g., status output) but acceptable given no output schema.

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 coverage is 100%, so description doesn't need to add parameter details. It does show parameter dependency via '->' notation, but this is already implied by schema optionality.

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 explicitly states 'Godot editor control' and enumerates two actions (launch: open editor, status: check if running). It differentiates from sibling 'project' by directing agents to use project(action='run') 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?

Provides explicit alternative for running the game, indicating when not to use this tool. However, it lacks broader exclusion guidance beyond that single case.

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