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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is fully covered. The description adds what the result contains, but it does not disclose how include_paused affects the returned set; this is acceptable for a safe read operation with an output schema, though not rich.

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, short sentence with no filler or repetition. It could be improved by making the action explicit and mentioning the include_paused caveat, but it is appropriately sized.

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 simple optional-parameter list with annotations and an output schema, the core information is present. The main gap is the unexplained include_paused parameter and the lack of any comparison with related recurring-rule or upcoming tools, leaving some ambiguity for an agent.

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 0% and the description never explains include_paused. The parameter name alone suggests it controls whether paused rules are included, but the default behavior and exact boolean semantics are left ambiguous.

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 clearly identifies the resource (recurring rules) and the displayed fields (next run, mode, paused state), so an agent understands what the tool exposes. However, it is a noun phrase rather than an explicit action and does not differentiate itself from add_recurring_rule or update_recurring_rule beyond the list-style title.

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?

No guidance is given on when to use this tool versus alternatives such as add_recurring_rule, update_recurring_rule, or upcoming. The read-only nature is only implied by the name and title, with no explicit context or exclusions.

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