get_recast_navmesh_settings

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the important scoping detail that it targets the editor world's default ARecastNavMesh (not an arbitrary navmesh or runtime instance), which is useful context beyond the annotations, but no auth, rate-limit, or failure-mode behavior is described.

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?

Two sentences, front-loaded with the action and target, followed by the return fields. The return enumeration is long but earns its place because no output schema exists for this tool.

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 zero-parameter read tool whose annotations already carry the safety profile, the description is complete: it names the exact object read, and since there is no output schema it hand-lists the returned fields (including recast_navmesh_present and success, which cover the not-found case). Nothing needed to invoke or interpret results is missing.

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 tool takes zero parameters, so per the rubric the baseline is 4. There are no parameter semantics to clarify, and the description correctly adds no misleading parameter information.

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 specific verb ('Reads') and a precisely scoped resource ('generation settings of the editor world's default ARecastNavMesh'). It clearly distinguishes itself from write-side siblings like set_recast_navmesh_settings by verb, though it doesn't name any alternative tool 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?

There is no when-to-use, when-not-to-use, or alternative-tool guidance anywhere in the description. The only usage signal is the verb 'Reads,' which leaves the agent to infer that this is the inspection counterpart to set_recast_navmesh_settings on its own.

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