geck_transaction_verify

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

With no annotations, the description carries the behavioral disclosure burden. The verb 'Verify' implies a non-destructive inspection, and the listed targets clarify what is checked, but the description does not explicitly state that no changes are made, whether it is safe to run anytime, or what happens if verification fails.

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 front-loaded sentence with no filler or repetition. It is appropriately concise for the amount of information it conveys, though the dense list of targets could benefit from a little more structure.

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 no annotations, no parameter documentation, and a broad family of overlapping sibling tools, the description is too thin to be fully actionable. The output schema covers return values, but the description does not explain prerequisites, expected usage flow, or how this verification differs from nearby state-inspection tools.

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 0%, so the description must compensate by explaining how backend, game_dir, and plugin_name relate to the verification targets. It does not mention any parameter or how plugin_name selects the plugin to verify, leaving the agent without additional semantic guidance beyond the raw schema names and defaults.

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 a clear action, 'Verify', and enumerates the resources involved: on-disk plugin state, active GECK plugin, placed records, and recent rollback points. It is understandable on its own, though it does not explicitly distinguish itself from overlapping siblings like geck_plugin_status, geck_active_plugin, or geck_transaction_list.

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 provides no guidance on when to use this tool versus related siblings, and it does not mention any exclusions or alternative tool choices. The transaction-related wording implies it may be used after transaction operations, but that connection is left entirely to inference.

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