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

No annotations are provided, so the description carries the burden. It does disclose that the tool is FREE and 'Informational only, not financial advice; verify with the firm', which is useful behavioral context. However, it says nothing about error handling, rate limits, or the shape of results for a multi-mode tool.

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?

A single dense but front-loaded block: purpose first, then action routing, then the disclaimer. Every clause carries information, though the parenthetical parameter list makes it read as a run-on.

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 10-parameter tool with no annotations and no output schema, the description covers purpose and mode routing but not return values (e.g., what a drawdown-room check yields) or parameter meaning. Adequate but with clear gaps.

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 10% (only 'program' is documented), so the description must compensate. It usefully names every check-mode parameter and flags the optional ones (startingBalance/currentBalance/highWaterMark/todayPnl/dayStartBalance/customDailyLoss), but it gives no meaning, units, or semantics for any of them.

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 domain (prop-firm drawdown and daily-loss rules) with three named modes: list_firms, get_rules, and a drawdown-room checker. An agent can immediately tell this is a prop-firm rule lookup/calculator, distinct from any sibling tool.

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 action enumeration plus the required-argument sketch for each mode ('get_rules (program)', 'check (program, accountSize, currentEquity...)') effectively tells the agent which mode to pick for which need. It lacks explicit when-not guidance, but the mode routing is clear enough.

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