find_nearby_nodes

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

With no annotations provided, the description carries full burden. It only states the prerequisite and basic action. It does not disclose what happens on success/failure, whether multiple nodes are returned, the coordinate system, or the order of results. This is insufficient for an AI agent to predict behavior.

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 very concise with two sentences, front-loading the critical prerequisite. However, it could be slightly more structured by separating the prerequisite from the action explicitly, though this is minor.

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?

Given the absence of an output schema, the description should explain what the tool returns (e.g., list of node paths or IDs). It does not describe return values, coordinate system units, or behavior for invalid inputs, leaving significant gaps for an AI agent.

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 input schema covers 100% of parameters with descriptions ('Search radius', 'Position as [x, y, z]'). The tool description adds no additional semantic value beyond what the schema provides, so it meets the baseline for high schema coverage but does not enhance understanding.

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 clearly states the tool finds nodes within a radius of a world position, using specific verbs ('Find') and a resource ('nodes'). The scope ('within a radius of a world position') distinguishes it from sibling tools like find_nodes_by_type or find_navigation_path, making the purpose unambiguous.

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 a prerequisite ('Game must be running') but offers no guidance on when to use this tool versus alternatives such as find_nodes_by_type or find_nodes_in_group. There is no mention of when not to use it or how to handle cases where no nodes are found.

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