iyke_timer_list

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

Description discloses sorting behavior and defaults, but no annotations exist. It lacks details on whether the operation is read-only, destructive, or requires auth, which would be useful for a tool with no annotations.

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?

Two sentences, zero waste. Information is front-loaded and every part adds value.

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 no output schema, description mentions sort order but not return fields. For a simple list tool with 2 optional params, it covers most essential information; however, missing output schema leaves some ambiguity about returned timer structure.

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%, so description must add meaning. It explains scope's default and status enum values, but does not specify scope's expected format (e.g., project ID). Overall, it partially compensates for missing schema descriptions.

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?

Description clearly states it lists timers in a scope, defaulting to the active project, with optional status filter, and sorting by fire_at ascending. This distinguishes it from sibling tools like iyke_timer_schedule and iyke_timer_cancel.

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?

Description implies usage for listing timers with optional filtering, and context from sibling tools suggests when not to use it (e.g., for scheduling/cancelling). However, no explicit when-not or alternatives are provided.

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