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

Beyond the readOnlyHint annotation, the description discloses key behavioral traits: the return is an actual image rather than a URL, the default returns only the main image, alle_bilder: true returns up to three additional views, and each call consumes context. This goes well beyond the annotation's minimal signal.

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?

Three sentences with no fluff. The purpose is front-loaded, followed by required inputs, default behavior, and usage caution. Each sentence adds a distinct and necessary piece of information without repetition.

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?

The description is complete for a simple read-only tool with no output schema. It tells the agent what the response is (image), how to get it (handle or product_id), what variants exist (main vs. all images), and the practical usage constraint. No required information is missing.

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 description coverage is 100%, so the baseline is 3. The description adds meaning beyond the schema by clarifying that handle or product_id come specifically from the search_flowers response and by explaining the default vs. alle_bilder behavior and the three-image cap. This enriches parameter understanding, though the schema already describes the fields accurately.

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 states a specific verb and resource ('Liefert das Foto eines Straußes als echtes Bild') and explicitly differentiates from a plain link, which distinguishes it from link-generating siblings. It also references the source response from search_flowers, making its role within the toolset unmistakable.

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 gives explicit when-to-use guidance: call it only for the one to three bouquets the customer is actually discussing, not for all search hits, and warns that each image costs context. It ties the required parameters to the output of search_flowers, which effectively routes the agent to the correct parent tool.

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