godot_resolve_uid

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

Annotations already indicate readOnlyHint=true and destructiveHint=false, so the description does not need to restate that. It adds little beyond the core behavior; for example, behavior on unresolved UIDs or whether resolution is project-scoped is not 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?

One direct, concise sentence with no filler. The verb is front-loaded and the input/output relationship is immediately understandable.

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?

The description is sufficient for a simple read-only lookup with one well-documented parameter and an output schema. It does not describe edge cases like missing or malformed UIDs, which would be the main gap.

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 uid parameter is named descriptively in the schema and the schema gives example uid:// strings. The tool description itself adds no parameter-level detail, but the overall purpose of the parameter is clear from the sentence.

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 verb, resource, and output clearly: take a uid:// identifier and return its file path. It is easily distinguishable from sibling tools like godot_get_uid and other file-related tools.

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 intended use is implied: when you have a UID and need the corresponding file path. However, it gives no explicit when-to-use or when-not-to-use guidance and does not mention the inverse sibling godot_get_uid.

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