manage_uids

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

With no annotations, the description carries full burden. It discloses that 'update' resaves all project resources, implying a potentially heavy/destructive operation, but does not clarify side effects, permission needs, or whether changes are reversible. The 'get' operation is not described regarding its output or side effects.

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 concise (three sentences) and front-loaded with the tool's purpose. It efficiently packs operation details and constraints. Slightly more structured formatting (e.g., bullet list) could improve scannability, but it is not verbose.

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 explains operations and error conditions, but lacks details on return values (e.g., what 'get' returns, confirmation for 'update'). The 'projectPath' parameter's role is not explained beyond being required. Given no output schema, the description should cover return behavior to be complete.

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 100% and each parameter has a description. The tool description adds value by explaining the purpose of each operation and linking parameters accordingly (e.g., filePath is required only for 'get'). This clarifies usage beyond the schema alone.

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 explicitly states 'Manage resource UIDs' and details two operations ('get' and 'update') with clear actions: retrieving a UID for a specific file and resaving all resources to regenerate UIDs. It distinguishes the tool's focus from sibling tools like add_node or create_scene.

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?

No guidance is given on when to use this tool versus alternatives. The only usage hint is the Godot version requirement and error conditions, but there is no mention of when not to use it or when another tool like get_project_files would be more appropriate.

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