cics_disable_transaction

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

Annotations already declare destructiveHint=true and idempotentHint=false; the description adds genuinely new semantics — that this is a gated write and that in-flight tasks are allowed to complete rather than being killed. It does not explain what the gate is (e.g. whether approve_write must be called first) or what the response contains, so it stops short of full disclosure.

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?

One compact sentence with the verb and resource front-loaded, followed by the scope note and the in-flight-tasks caveat. No filler, and the most decision-relevant facts come first.

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 5-parameter mutation tool: annotations carry the destructive/idempotent profile, the schema documents every parameter, and there is no output schema to explain. The only real omission is the unresolved meaning of 'gated write' and what the tool returns on success.

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 100%, so all five parameters, including the enable-inversion behavior, are already documented in structured form. The description restates the ENABLESTATUS mapping without adding format or constraint detail beyond the schema, so the baseline 3 applies.

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?

A specific verb and resource — 'Disable a CICS local transaction' — plus the exact CMCI mechanism (SET with ENABLESTATUS=DISABLED). The schema's enable flag is echoed, so an agent can tell this apart from list_cics_transactions or cics_newcopy immediately.

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?

'New work is refused; in-flight tasks finish' implies the operational reason to use it (quiescing a transaction) but never states when to choose it over alternatives or when not to use it. 'Gated write' hints at a prerequisite step without naming it, leaving the agent to infer how the gate is satisfied.

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