image_generate

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

No annotations are provided, so the description carries the full burden. It discloses key behavioral traits: submits the job, polls until complete with a 5-minute timeout, and returns the image URL/path. This gives the agent a clear model of the async behavior and time cost. It does not mention error handling or failure outcomes, but the core behavior is well covered.

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 concise and front-loaded: the first sentence states the purpose, and the second explains the workflow. Every sentence earns its place, and there is no redundant information.

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 with 5 parameters and no annotations or output schema, the description provides a solid overview: what it does, how it works (submission and polling), and what it returns. It could also mention potential failure modes or prerequisites (e.g., local service running), but the combination of schema descriptions and this overview makes the tool reasonably complete for agent use.

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?

The input schema covers 100% of the parameters with descriptive text, including enums and defaults. The description itself adds no additional parameter semantics beyond what the schema already provides. Therefore, the baseline score of 3 is appropriate.

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 the tool's function: 'Generate an image using Fooocus (Stable Diffusion XL) running locally.' The verb 'Generate' plus the resource 'image' is specific and unambiguous. It also distinguishes from all sibling tools, which are focused on memory, conversation, system, or security tasks, making this the only image generation tool.

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 does not explicitly state when to use this tool versus alternatives, but the sibling list contains no similar image generation tools, so the usage context is implicitly clear. It also provides useful behavioral expectations (submit and poll) that help the agent decide when to invoke it appropriately.

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