read_tilemap

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

With no annotations provided, the description carries full responsibility for disclosing behavior. It only states it reads TileMapLayer, but does not mention return format, what happens if no TileMapLayer exists, whether it reads all such nodes or only the first, or any side effects. The read-only nature is implied by the verb but not explicitly stated, leaving significant behavioral gaps.

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 with no filler or redundant words. It is front-loaded with the verb and direct object. While it could include more detail, it is appropriately brief for a straightforward read operation.

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?

The tool is simple with one parameter, but without an output schema, the description should at least hint at the return value or data shape. It does not. The description is too sparse to be considered complete for an AI agent to know what to expect from the invocation, especially in a broader scene-editing context.

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 already provides 100% coverage for the single parameter scene_path with a clear description ('Path to .tscn scene containing TileMapLayer nodes'). The tool description adds no additional meaning beyond what the schema states, so the baseline score of 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 'Read TileMapLayer in scene' clearly identifies a specific read operation targeting TileMapLayer nodes within a scene. It uses a verb+resource structure and distinguishes itself from sibling tools like read_tileset and read_scene by naming the specific node type. However, it is terse and could be more explicit about returning layer properties.

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 by stating the action ('read') and target ('TileMapLayer in scene'), so an agent can infer when to use it. However, there is no explicit guidance on when not to use it or which alternatives (e.g., read_tileset) are better suited for other scenarios. No prerequisites or exclusions are mentioned.

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