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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds meaningful beyond-schema context: provider access can fail, nothing is purchased or saved publicly, warnings must be shown and the player chooses swaps, and bracket analysis is guidance not certification. This is solid added context, though return-format details are only lightly touched.

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?

Dense but front-loaded: the core action and accepted input forms come first, then constraints, then output expectations. Every sentence carries information, though the paragraph is long and could be broken up for scannability.

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 description carries the return-value burden and does so well (cuts/additions, role counts, warnings, estimated cost, card links, TCGplayer cartUrl). Combined with the safety context, it is complete enough to call correctly, with only minor gaps around 'bracket' and 'maxChanges' semantics.

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 low (22%), so the description does meaningful compensating: it explains deck, commander, budget as USD, replaceCard restriction to one non-protected card, owned entry/copy limits, and locked/excluded as newline-separated names. It still leaves 'bracket' (the 1-5 target) and 'maxChanges' unexplained, so it does not fully close the gap.

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?

States a specific verb+resource ('Review a Commander bracket transition using bracketshift') and distinguishes the operation from the sibling set implicitly. It does not explicitly name any sibling tool to contrast with, so it lands at 4 rather than 5.

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 concrete input guidance (decklist or HTTPS Moxfield/Archidekt URL, fallback to plain-text export on provider failure) and the replaceCard narrowing behavior. However, there is no explicit when-to-use-this-vs-siblings guidance (e.g. vs find_replacements or reduce_deck_cost), leaving tool selection to inference.

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