get_navmesh_status

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It says 'Return' which implies a read-only operation, but it does not explicitly state that no scene mutation occurs, what data is included, or whether the status reflects the current simulation state. The meaning of 'Navigation Core, NavMeshVolume, bake and area status' is left underspecified, so an agent cannot anticipate the exact response semantics.

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 redundant wording, which is structurally clean. However, it is terse to the point of underspecification, leaving key details about status scope and parameters unstated. This is closer to minimal viability than genuine conciseness.

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?

Despite the presence of an output schema, the description lacks essential context: parameter semantics, when to call this tool, and what 'Navigation Core, NavMeshVolume, bake and area status' actually covers. For a getter with no annotations and zero param documentation, the description is insuffficient for an agent to confidently invoke it without additional inference or trial.

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 0%, and the description does not mention command_id or idempotency_key at all. The parameters are optional but their purpose — such as associating the call with a prior bake command or ensuring idempotent retries — is completely undocumented. The description adds no value beyond the raw schema.

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 states a clear verb ('Return') and resource ('Navigation Core, NavMeshVolume, bake and area status'). It indicates this is a status-read operation and is distinct from action-oriented siblings like bake_navmesh. However, it does not explicitly differentiate itself from other status tools like get_runtime_status or get_ros2_status, though the navmesh focus provides some inherent separation.

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 provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites (e.g., whether a navmesh must be baked first) or contrast with bake_navmesh or other status queries. An agent must infer usage solely from the tool name and the vague description.

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