feegow_get_product_position

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

Discloses read-only nature (no data changes), pagination method, and date format. With no annotations, this provides essential safety and usage context beyond the schema.

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?

Single sentence conveys purpose, method, behavior, and endpoint. No wasted words; front-loaded with key intent.

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?

Adequate for a query tool: covers input parameters, pagination, date format, and read-only nature. Lacks return structure, but no output schema exists, and typical position queries suffice with this info.

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 has 100% parameter description coverage, so the description adds only marginal value (e.g., default pagination values). Baseline 3 is appropriate.

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 it retrieves product stock position, explicitly labels it as a query (CONSULTA), and distinguishes it from sibling product manipulation tools like entry/exit/movement.

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?

States it's a read-only operation despite POST, which prevents misuse. Does not explicitly contrast with alternatives, but the context of stock query versus entry/exit is implicit.

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