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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so safety is covered. The description adds real domain context beyond that: the one-minute polling cadence, the fire-once semantics of conditional orders, and the meaning of each lifecycle status. It still omits ordering, retention, and any rate/volume limits on a polling-backed list endpoint.

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?

Four tight sentences, front-loaded with the action, then mechanism, status glossary, and return shape. No filler; each sentence removes a plausible ambiguity for an agent choosing between the many order tools.

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 correctly supplies the return shape (paginated results containing conditions summary, action, status), and the safety profile is carried by annotations. Pagination controls are documented in the schema, so an agent has everything needed to call it correctly.

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% (limit default 20/max 100, offset default 0, enum-style status list), so the baseline is 3. The description enriches only two of the five status values ('active (monitoring)', 'executed (fired)'), which is a marginal addition over the schema's own list.

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?

'List the user's conditional orders' gives a specific verb+resource, and the plural plus the follow-up explanation of rule-based monitoring clearly separates it from the singular get_conditional_order and from mutators like create_conditional_order or run_conditional_order. It does not explicitly name those siblings, so it falls short of the 5-level routing clarity.

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 description never states when to call this versus get_conditional_order (single order), get_suggested_orders, or run_conditional_order. Usage is only implied by the tool name; there are no exclusions, prerequisites, or alternative-selection guidance.

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