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

With no annotations provided, the description carries the full burden of behavioral disclosure. The sentence 'Generating an image with this model consumes credits' adds valuable context beyond the literal 'get information' action, warning the agent about consequences associated with the model itself. However, it does not confirm whether the tool is read-only or disclose any other side effects, though the verb 'get' is strongly suggestive.

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 concise sentences carry the core purpose and a behavioral warning. No wasted words, and the key action is front-loaded. This is appropriately sized for a read-only tool with a single parameter.

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 the absence of an output schema, the description states what the tool returns (full capabilities and price) but does not clarify how to identify valid model inputs or reference the sibling list_image_models as sourcing. For a tool with a single parameter and no output schema, the description is mostly adequate (3), but it doesn't fully compensate for the missing parameter guidance and alternative routing information.

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 provides no description for the 'model' parameter (0% coverage). The description's phrase 'one image model' gives only a loose hint, but does not define what values are valid, whether it accepts a model ID from list_image_models, or any format expectations. With such low schema coverage, the description should have provided semantic details about the input, but falls short.

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 ('get') and clearly identifies the resource as 'one image model'. It distinguishes itself from the sibling get_video_model by specifying 'image' and from list_image_models by emphasizing 'one model', making its purpose clear and unambiguous.

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 implies a singular focus (one model) but does not explicitly state when to use this tool versus list_image_models or get_video_model. It provides no exclusions or alternative routing, though the context of 'one image model' gives a partial hint that this is for a specific model rather than a list.

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