godot_resource_inspect

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

With no annotations, the description carries the full behavioral burden. It does disclose that the operation does not modify the resource, but it says nothing about permissions, supported resource types, failure modes, or what information is returned.

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 single sentence is front-loaded and contains no wasted words. However, it is under-specified rather than appropriately concise for a tool that must be selected correctly among many siblings.

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 tool has a simple schema and no output schema, but an inspection tool should still state what it returns, what resource types it handles, and how to interpret the path. None of that is present, leaving key usage context 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?

There is one required parameter, path, and schema description coverage is 0%. The description does not explain whether the path is a res:// path, a filesystem path, or which resource types are accepted, so the parameter remains ambiguous.

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 states a specific verb-resource pair: inspect a project resource. It also clarifies the operation is non-modifying. However, it does not distinguish this tool from nearby siblings such as godot_scene_inspect or godot_resource_leaks, so an agent must infer the boundary.

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 no guidance on when to use this tool versus alternatives like godot_scene_inspect, godot_project_info, or godot_resource_leaks. There are no stated preconditions, exclusions, or routing cues.

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