Find Godot Executable

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

Annotations already mark readOnlyHint, and the description adds meaningful behavioral detail: search mechanisms (mdfind, where.exe, find, directory scan, PATH), OS-specific ordering, and return contents. It stops short of stating failure behavior or what happens when GODOT_EXECUTABLE is set, but there is no contradiction.

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 front-loaded with purpose, then uses compact OS-specific bullets that carry real operational information. Every line earns its place and the return type is stated clearly.

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 parameterless read-only lookup, the description is complete: it covers all platforms, the fallback order, and the return shape, while the output schema handles formal return typing. Nothing essential 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 has zero parameters and schema coverage is complete, so there are no parameter semantics to document. The description still clarifies the implicit environment-variable input (GODOT_EXECUTABLE) and the resolution context, which is useful.

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 the exact resource (the Godot executable) and a specific action (find), and adds OS-specific resolution order that makes it distinct from sibling search tools aimed at files, assets, or projects. It is immediately clear what this tool returns.

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 gives clear context by specifying behavior when GODOT_EXECUTABLE is unset and enumerating platform resolution strategies. It does not explicitly contrast itself with siblings or say when to call it before run/script tools, but the purpose is unambiguous.

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