advise

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

No annotations provided, so description carries full burden. Mentions table_id must be hero's turn, but lacks details on whether tool is read-only, side effects, or what 'mc_trials' default implies. Leaves behavioral gaps.

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?

Two clear sentences plus args list. Front-loaded purpose, no wasted words. Ideal length for a simple tool.

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?

Tool is simple with 2 params and output schema exists. Description covers key points (hero turn, mc_trials purpose). Could mention output type or that no state is changed, but output schema likely provides that.

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 0%, so description compensates well. Adds meaning: table_id requires hero's turn, mc_trials defines equity estimate rollouts. Could add constraints like range for mc_trials.

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?

Description uses specific verb 'Recommend' and resource 'hero action', clearly stating it combines equity, pot odds, and preflop charts. This distinguishes it from siblings like 'calc_equity' (equity only) and 'submit_action' (execution).

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?

Usage is implied: call when you need a recommended action during hero's turn. No explicit when-not-to-use or alternatives mentioned. Could improve by stating not to use for executing actions or calculating raw equity.

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