xmorf_edit_image

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

With no annotations, the description bears full responsibility for behavioral disclosure. It explains the input format (file path or base64) and several model behaviors, but omits details on side effects, authentication needs, rate limits, return format (base64 vs. file save), or limitations (e.g., file size constraints).

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: first sentence states purpose, second lists models and input formats. No redundant or empty phrases. The information is front-loaded and efficiently packed.

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?

No output schema is provided, so the description should clarify the return value (base64 image data or file saved). This is missing. Additionally, it lacks guidance on image size limits, required permissions, or error handling. For a tool with 5 parameters and no annotations, the description is incomplete.

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?

Input schema coverage is 100%, so baseline is 3. The description adds value by clarifying that the 'image' parameter can be a file path or base64 data URL, and it explains the purpose of each model value beyond the enum labels, e.g., 'shadow (light migration, needs reference)'.

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 clearly states 'Edit an image using AI with a natural language prompt', which is a specific verb and resource. The list of models adds detail but does not explicitly differentiate from sibling tools 'xmorf_generate_image' and 'xmorf_list_models', though the edit vs generate distinction is implicit.

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 lists models with brief purposes (e.g., 'enhance (realism)', 'shadow (light migration, needs reference)'), providing some guidance on when to use each. However, it does not explicitly contrast with the 'generate' sibling (which creates new images) or provide exclusions or prerequisites.

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