grocy_stock_transaction

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true, so the safety bar is lower. The description adds that undo 'reverts' a transaction and that undo 'needs confirm', which is real behavioral context beyond the annotations. It does not say whether the undo is reversible, what 'reverts' means concretely for stock levels, or that omitting confirm yields a dry run (that detail lives 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 sentences with no padding, and the mode behaviors are front-loaded. The only weak spot is the throwaway opener 'Stock transaction.', which restates the name instead of adding information.

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 two-mode tool with no output schema and only partial schema descriptions, the description covers the actions but not the outcome: it doesn't say what the get response looks like, what undo returns, or what happens to stock after a revert. An agent can pick the right action but cannot fully predict the effects.

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 only 33%: the action enum and confirm are documented in the schema, but transaction_id has no description anywhere. The description partially compensates by explaining what each enum value does (get lists bookings, undo reverts), which is value beyond the raw enum. It leaves the required transaction_id entirely unexplained – what a transaction id is and where to obtain it remains unclear.

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 names the resource (stock transaction) and enumerates the two modes: 'action get lists bookings' and 'undo reverts the transaction'. However, the opening phrase 'Stock transaction.' is a noun fragment rather than a verb+resource statement, and it never distinguishes this tool from close siblings such as grocy_stock_booking or grocy_stock_entry, so the agent must infer the boundary.

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?

It implies when each action applies (get to list bookings, undo to reverse one) and notes undo requires confirm, which is genuinely useful routing information. It gives no explicit guidance on when to prefer this over sibling booking/stock tools, and no exclusion conditions, so usage is inferred rather than stated.

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