list_timers

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

No annotations exist, so the description carries full burden. It only states 'List timers' which implies a read operation, but does not disclose any behavioral traits such as scope (all channels vs current), ordering, or side effects. This is minimal transparency.

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?

One short phrase, no wasted words. Every word is essential and the description is front-loaded with the key action and resource.

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?

Given zero parameters and the presence of an output schema (available but not shown), the description is mostly complete. It could clarify whether timers are for the current channel or globally, but overall it is adequate for a simple list operation.

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 has zero parameters, and description coverage is 100% (no params to cover). Baseline for 0 parameters is 4, and description adds no unnecessary information. No additional semantics needed.

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 'List timers (scheduled recurring chat messages)' uses a specific verb (List) and resource (timers), and clarifies what timers are with parentheses. This clearly distinguishes it from sibling tools like add_timer, toggle_timer, delete_timer.

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 on when to use this tool vs alternatives. It implies use for viewing timers, but lacks explicit context or when-not-to-use instructions. Sibling tools include many unrelated ones, but no differentiation is provided.

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