Изображение ассета

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real value by disclosing the return shape (PNG block plus size/format info) and resize behavior, but it does not spell out the side effect of writing a PNG to the `out` path, which sits awkwardly against the read-only hint.

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?

Two sentences, front-loaded with the return behavior before the parameter note, with no filler. Slightly dense parenthetical, but every clause earns its place.

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?

With no output schema, the description correctly takes on the burden of describing the return (PNG block plus size/format summary), and it covers the one undocumented parameter. What remains thin is the file-output side effect and any relation to sibling tools, but for a simple read-and-render tool this is close to 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 67% and the `size` parameter has no schema description at all; the description compensates by defining it as a square resize where 0 means no change. `path` and `out` are already documented in the schema, so the description fills the meaningful gap without redundancy.

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 and resource — it returns a project texture rendered as a PNG block plus size/format metadata — which distinguishes it from generic siblings like godot_status or godot_files. It does not explicitly separate itself from godot_screenshot, the closest sibling, so it stops short of a 5.

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?

It supplies a use case ('визуальная проверка спрайтов, иконок, атласов'), which implies when to reach for it, but never states when not to use it or names an alternative such as godot_screenshot or godot_assets. Usage is inferred rather than directed.

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