feegow_exit_product

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

Without annotations, description partially covers behavioral traits: identifies as write operation, requires FEEGOW_ALLOW_WRITES=true. Lacks details on side effects, idempotency, error responses, or rate limits.

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?

Two short sentences plus tags, front-loaded with purpose, no extraneous information. Efficient and well-structured.

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 19 parameters, no output schema, and no annotations, description fails to explain return values, error handling, or how this tool fits with sibling inventory tools. Completeness is insufficient for complex mutation.

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 coverage is 100% so baseline 3 applies. Description reinforces date format but adds little beyond schema property descriptions; does not clarify parameter usage beyond what schema already provides.

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?

Description clearly states it records product exits from inventory ('Registra a saída de produtos do estoque'), using specific verb and resource. It distinguishes from sibling 'feegow_entry_product' which records entries.

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?

Provides context for usage by stating it's a write operation requiring FEEGOW_ALLOW_WRITES=true, but does not explicitly list when or when not to use it, nor compare with alternatives like feegow_entry_product or feegow_movement_product.

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