godot_editor_read

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

No annotations are provided, so the description bears the full burden for behavioral transparency. It only states 'Read-only' and lists actions, without disclosing error behavior, side effects, or requirements. Minimal value added beyond the 'Read-only' label.

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 concise (one sentence) and front-loaded with the 'Read-only' purpose. However, the list of actions could be structured better (e.g., bulleted) for clarity.

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 30+ siblings, 2 parameters with minimal schema, and no output schema, the description is too sparse. It fails to explain what each action does, how to use 'params', or what the return value looks like, leaving significant gaps for the agent.

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 0% description coverage for parameters, but the description enumerates possible values for 'action' ('state,selection,open_scenes,viewport,performance'), adding meaning. However, no detail is given for the 'params' parameter, leaving ambiguity.

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 it is 'Read-only editor state' and lists actions, making the tool's purpose clear. It distinguishes from the sibling 'godot_editor_edit' implicitly as read-only, though not explicitly.

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 implies usage for reading editor state via 'Read-only', but provides no guidance on when to use this tool over other sibling tools like 'godot_node_read' or 'godot_runtime_state', nor any conditions or when not to use it.

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