read_area

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states 'Read', implying non-destructive behavior, but does not mention return format, error handling, or any constraints (e.g., scene file requirement, editor-only operation). This is a meaningful gap for a tool with no annotations.

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 concise sentence that states the core purpose without waste. It is front-loaded and efficient, though it could arguably do more with that space given the lack of guidance elsewhere.

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 tool with no annotations, no output schema, and only 2 parameters, the description is thin. It does not explain return values, when to use this read tool versus alternatives like read_collision_layers, or any prerequisites. The context is incomplete for an agent to invoke it correctly.

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%—both parameters have descriptions ('Path to .tscn scene' and 'Area2D/3D node name'). The tool description adds no parameter details beyond the schema, so the baseline of 3 applies.

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 'Read Area2D/3D properties' uses a specific verb (Read) and resource (Area2D/3D properties), clearly indicating the tool's purpose. It stands out from sibling read_* tools by targeting a specific node type, though 'properties' is somewhat generic.

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?

No guidance is provided on when to use this tool versus alternatives. With many sibling read_* tools (e.g., read_collision_layers, read_camera), there is no explicit or implicit usage context to help an agent choose this over others.

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