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

Beyond the annotations it discloses the traits an agent actually needs: persistence past the session end ("TradeHub keeps watching after this session ends"), a hard cap of 5 rules, each rule firing exactly once, the two possible outcomes (notify via Telegram/events/webhooks, or a reduce-only partial close), and replacement semantics ("A new plan replaces the old; rules=[] removes it"). There is a mild tension with destructiveHint=false given that a rule can close position size, but the description's "reduce-only" wording mitigates it and no annotation is directly contradicted.

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?

Front-loaded with the when-to-use condition and examples, then behavior, then the next tool — a sensible order with no filler sentences. The style is telegraphic (sentence fragments, quoted examples), which is efficient but slightly staccato compared with fully formed prose.

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 mutating scheduler with nested rule objects, the description covers the lifetime of the plan, the rule cap, the fire-once semantics, both action modes, and how to clear a plan. Output schema exists and parameters are fully documented in the schema, so nothing an agent needs in order to invoke it correctly is missing.

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 100%, so the baseline would be 3, but the description earns more by mapping natural-language requests onto concrete parameter combinations: "close half below 94000" ties price_below to action=close with close_fraction, and "funding passes 50% a year" ties funding_above to the yearly-fraction value. It also explains the empty-array case for rules, which the schema notes only in passing.

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 states a specific action on a specific object: it sets deferred conditional rules on a held position that either notify the person or reduce-only close part of it. It explicitly separates itself from the nearest sibling with "Not a stop-loss" and points forward with "Next: get_my_positions", so an agent can place it among set_stop_loss_rule, set_price_alert, and close_position without opening any schema.

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?

It names the triggering user intents with three literal example quotes ("close it if still open in 3 days", "tell me if its funding passes 50% a year", "close half below 94000"), gives the exclusion ("Not a stop-loss"), and states the capability boundary ("you cannot schedule checks yourself"). The usage conditions and the alternative are both explicit.

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