read_nav_region

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

With no annotations provided, the description must disclose behavioral traits, but it only says 'read', giving no information about side effects, required state, or error behavior. It doesn't contradict annotations (none exist), but it also doesn't add meaningful transparency.

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 extremely short ('Read navigation region'), which is concise but under-specified. It lacks structure—no sentence for behavior, parameters, or examples. Conciseness is not valuable when it omits critical meaning.

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?

This is a tool with no annotations, no output schema, and a minimal description. There is no mention of what the return value contains, how to use the region_name parameter, or any context about navigation regions. Completely inadequate for an agent to invoke 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%, with both scene_path and region_name having descriptions. The tool description adds no parameter information but doesn't need to since the schema already covers it. Baseline 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 names a specific verb ('Read') and resource ('navigation region'), which prevents confusion with read_nav_agent or read_nav_obstacle. However, it doesn't explain what 'read' means in this context—what properties are retrieved or what constitutes a navigation region—so the purpose remains vague.

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 like read_nav_agent, read_nav_obstacle, or list_nav_regions. The description lacks any context about prerequisites (e.g., scene loaded) or exclusions.

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