resource_get_uid

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

No annotations are provided, so the description carries full burden. It only states 'get the UID' without disclosing whether it's read-only, requires an open project, or error behavior. Output schema exists but 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?

The description is short and front-loaded with the purpose. It uses a heading for category and lists arguments clearly. It could be slightly more concise, but no unnecessary text.

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?

Output schema exists, so return details are not required. However, the description lacks context on prerequisites (e.g., project must be open), error handling, or limitations (e.g., only works with Godot 4.4+ projects). Adequate but missing key operational details.

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 coverage is 0%, but the description adds helpful context: project_path is 'Path to the Godot project directory' and file_path is 'Path to the file (relative to project) for which to get the UID'. The 'relative to project' detail is valuable beyond the schema's plain 'string' type.

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 'Get the UID for a specific file in a Godot project', specifying the resource and action. It distinguishes from sibling tools that deal with different resources (materials, mesh libraries) or actions (list, create).

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 basic context (Godot 4.4+, Resource category) but does not explicitly state when to use this tool versus alternatives, nor does it mention when not to use it. The specialization makes it implicit, but no direct guidance is given.

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