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

Excellent disclosure of snapshot nature, real-time polling requirements, timing constraints (1 second intervals), and response flags (continue_polling, display_mode) with no annotations present to contradict.

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?

Extremely verbose due to massive DISPLAY INSTRUCTIONS section with Unicode block examples and formatting rules that dilute the core tool semantics; front-loaded purpose saves it from being a 1.

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?

Adequately covers the complex polling interaction pattern and acknowledges output structure (Dict with progress data) without unnecessarily duplicating output schema details.

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?

Compensates for 0% schema description coverage by clarifying rule_name is the 'Rule being executed' and critical context that execution_id comes from execute_rule().

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?

Opening sentence clearly states it fetches execution progress for running rules, though this is somewhat buried under extensive display formatting instructions.

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?

Explicitly details the polling pattern (call every 1 second), when to continue vs stop (continue_polling flag), and relationship to execute_rule (execution_id source).

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