create_purchase_intent

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It only states that a new purchase intent is created, without mentioning side effects, authorization requirements, rate limits, failure modes, or idempotency.

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 front-loaded with the purpose, followed by a structured parameter list. It is concise with no wasted words, though the title line and first sentence are slightly redundant. Overall, it earns its length.

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 tool has 6 parameters, no output schema, and no annotations, the description covers the basic creation purpose and parameter descriptions but lacks details on return values, error handling, or prerequisites. It is adequate but not fully comprehensive.

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 0%, so the description must compensate. It provides German-language descriptions for all 6 parameters (e.g., 'Beschreibung des gewünschten Artikels' for item), adding meaning beyond the schema's titles and types. Descriptions are brief but sufficient.

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 'Strukturierte Kaufabsicht erstellen' and 'Erstellt einen neuen Kaufvorgang', identifying the verb (erstellen) and resource (Kaufabsicht/purchase intent). It also distinguishes from sibling tools like compare_offers and track_purchase by explaining that this purchase intent is then compared and tracked.

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 indicates when to use this tool: to create a purchase intent that will later be compared with offers and tracked. It implies this is the first step in a workflow, but does not explicitly state when not to use it or mention alternative tools.

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