gimp_pdb_call

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

Annotations already declare destructiveHint=true, readOnlyHint=false and openWorldHint=false, so safety is partly covered. The description adds real behavioral context beyond that: 'run-mode' defaults to NONINTERACTIVE (no dialogs), special placeholder substitution rules, and how file/color values are interpreted. It does not warn about side effects of arbitrary procedures, but the added semantics are substantive.

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?

Front-loaded with the core purpose, then a compact semicolon-delimited list of special-value rules. Dense but every clause carries information; the parenthetical special-value list is slightly hard to parse but nothing is wasted.

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?

For a tool that can invoke any PDB procedure, with no output schema and 0% parameter description coverage, the description covers the key input conventions but says nothing about return format, error behavior on unknown procedure names, or how results come back. Adequate but with clear gaps for such an open-ended tool.

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 description coverage is 0%, so the description must carry the load, and it does: it maps image_id to 'image', layer_id to 'drawable'/'drawables', and describes the named-arguments object and file/color value formats. The 'arguments' object and 'name' semantics are only implied rather than spelled out, leaving a small gap.

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?

States a specific verb and resource: 'Llama a cualquier procedimiento PDB por nombre con argumentos por nombre.' An agent can tell this is the generic escape-hatch for arbitrary PDB procedures, distinct from the many task-specific siblings like gimp_draw or gimp_fill. It stops short of explicitly framing itself as the fallback when no specialized tool exists, which keeps it from 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?

The only routing guidance is 'Consulta antes gimp_pdb_info' (check gimp_pdb_info first), which is a useful discovery step. It never states when to prefer this generic call over the dozens of purpose-built sibling tools, nor any when-not-to-use condition, so usage is only implied.

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