grocy_stock_booking

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false and openWorldHint=true; the description usefully reinforces that undo is a confirm-gated POST. It adds nothing about permissions, whether undo restores previous stock levels, or error behavior for a nonexistent booking, and the dry-run preview is disclosed only in 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?

Three short clauses, front-loaded with the resource and then per-action behavior. No filler and every sentence carries information an agent needs.

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?

With no output schema, the agent gets no hint of what a get returns (booking fields, product, quantity) or what undo affects on stock levels. For a two-mode tool with a write path, the description should say more about results and preconditions.

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 only 33%, so the description carries real weight: it maps action values get/undo to concrete endpoints and identifies bookingId as a path parameter, compensating for the undescribed enum. It still says nothing about booking_id validity or scope beyond the schema's integer constraints.

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?

Names the resource (stock booking) and enumerates both operations with their underlying endpoints: get a booking by ID and undo a booking. This is enough to separate it from siblings like grocy_stock_consume or grocy_stock_add, though it never explicitly contrasts with them.

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?

Implies selection between the two actions (use get to read, undo to reverse) and states undo requires confirm, but gives no guidance on when this tool is preferable to adjacent stock tools such as grocy_stock_consume, grocy_stock_transaction, or grocy_stock_product.

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