luceed_cijene

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that prices are current and include promotions, but it does not state the read-only nature explicitly, nor does it describe authentication, rate limits, or return format.

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 short and front-loads the core resource. There is slight redundancy between 'Current prices' and 'Current selling price', but no wasted sentences.

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 seven parameters and conditional action modes, the description does not explain which parameters apply to which action (e.g., partner and tip_partner for partner action, username for loyalty). With no output schema, it also does not describe the response shape or what price fields are returned.

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 schema already documents all seven parameters. The description confirms the action values but adds no additional meaning about how action-specific parameters such as partner, tip_partner, username, or valuta are used.

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 the resource and scope clearly: 'Current prices' and 'Current selling price including promotions.' It also lists lookup modes, but it does not explicitly distinguish this tool from nearby siblings such as luceed_cjenik or luceed_cjenik_partner.

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?

Listing the action values ('sifra, barcode, partner, loyalty') implies the available lookup modes, but the description gives no explicit when-to-use guidance or alternatives to sibling pricing tools. The agent must infer that these actions select the lookup method.

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