gimp_pdb_call

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

With no annotations, the description carries the full burden of behavioral disclosure. It explains the encoding conventions (ids, strings, enums) but does not disclose potential side effects, undo behavior, or error handling. Saying it can call 'any PDB procedure' hints at broad reach, but does not explicitly warn about destructive or state-mutating calls.

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 two tight sentences with no filler. The core action is front-loaded, and the second sentence delivers the most important parameter-encoding rules an agent needs before invoking.

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 covers the essential invocation contract and an output schema exists, so return values need not be explained. However, for a generic no-annotation execution tool, it omits guidance on discovering valid PDB procedure names/signatures via gimp_pdb_describe, and it leaves undo_group semantics unstated. These gaps make it minimally viable but not fully 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 description coverage is 0%, so the description must compensate. It does this well for the opaque args object by stating that arguments are keyed by name and that images/items are passed as ids, colours as strings, and enums by nick. However, the undo_group parameter is not explained, 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?

The description uses a specific verb and resource: 'Call any PDB procedure by name'. It also clarifies the calling convention with arguments keyed by name. This clearly distinguishes it from search/describe siblings like gimp_pdb_search and gimp_pdb_describe, which do not invoke procedures.

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 phrase 'any PDB procedure' implies this is the generic raw invocation tool, but the description does not explicitly say when to prefer it over specialized siblings or when not to use it. There is no mention of alternatives or exclusions, leaving the usage context mostly implicit.

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