gerent365_kiosko_products

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

With no annotations provided, the description carries the full burden. It discloses the authentication requirement (kioskCode + pin) and that it returns 'productos disponibles', but does not mention return format, error behavior, or side effects beyond the read-only verb 'Obtiene'. Some useful context is given, but it is not comprehensive.

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 a single concise sentence that front-loads the main purpose and then adds authentication context without any waste. It is appropriately sized for the tool's simplicity.

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 simple schema, no annotations, and no output schema, the description covers the core intent and authentication requirement, but leaves ambiguity about how optional parameters interact with environment defaults and the exact meaning of 'productos disponibles'. It is minimally sufficient but not fully self-contained.

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 already provides full descriptions for both parameters (100% coverage), so the baseline is 3. The description adds minimal value by noting they are used together for authentication, but does not clarify behavior around optionality (e.g., how env defaults apply). No further parameter details are provided.

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 action ('Obtiene') and resource ('productos disponibles desde el kiosko'), specifying a distinct scope (kiosk) that differentiates it from the sibling gerent365_list_products. The authentication context further refines its purpose.

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 usage in a kiosk-authenticated context by mentioning 'autenticado con kioskCode + pin', but it does not explicitly state when to choose this over alternatives like gerent365_list_products or provide exclusions. The guidance is implied rather than explicit.

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