gimp.procedure.call

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

With no annotations, description bears full burden but only states 'Call a GIMP PDB procedure' without detailing side effects, permissions, or error conditions, leaving behavioral traits unclear.

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 efficient sentences with front-loaded purpose and zero waste; every clause adds value.

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?

Given no output schema and two parameters, description covers usage flow and argument format but lacks return value and error context; adequate but not comprehensive.

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 50%; description adds format guidance for 'args' but not for 'name'. It clarifies how to structure object arguments beyond the schema's minimal description.

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?

Description clearly states the verb 'call' and resource 'GIMP PDB procedure', distinguishing it from sibling tools like gimp.procedure.describe and gimp.procedure.search.

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?

Explicitly advises to 'Use describe first' and provides format guidance for arguments ('pass object arguments as {"id": 123} or typed refs'), aiding correct invocation.

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