Get image model capabilities

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

No annotations are present. The description explicitly states the operation is to 'Describe' and enumerates the exact result fields ('required image count, mask policy, size support, prompt requirement, JSON Schema for parameters, parameters example'), which signals a read-only introspection behavior and sets expectations for what is returned. It does not discuss errors or permission requirements, but for a capability-definition query this is adequate.

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 compact: one purpose sentence, one sentence on result contents, and an Args block. The Args block is duplicative of the schema, but the overall length is appropriate and the key information is front-loaded.

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 only one required parameter and an output schema present, the description need not detail return structures. It covers the operation's intent and the key included fields, making the tool self-contained. It could mention sibling tool alternatives, but that omission affects the usage dimension more than completeness.

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 100%; the `model` parameter is already described in the schema as 'Enabled tai-openapi image edit model alias to inspect.' The description's Args section repeats this rather than adding new semantics, so it earns the baseline 3.

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 opens with 'Describe the exact inputs accepted by one enabled image edit model,' which names a clear verb ('Describe'), resource ('image edit model capabilities'), and scope ('one enabled...'). This distinguishes it from sibling tools like list_image_models or edit_image.

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?

No explicit 'when to use' or alternative references appear. The description implies you should call this when you need a model's input contract, but it does not contrast with list_image_models or edit_image, so guidance is only implicit.

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