List Scheduled Jobs

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, covering safety and behavior. The description adds that it returns next-run time, interval, and disabled state, but no additional behavioral traits (e.g., pagination, sorting) are disclosed. The description adds minimal value beyond 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?

Single sentence, no filler words. All content is relevant and essential. Efficiently conveys purpose and key output details.

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?

Although no output schema is provided, the description lists the key fields returned. For a simple list operation with well-defined parameters and rich annotations, this is largely complete. Minor improvement would be mentioning typical use context (e.g., before managing jobs), but not required for basic usage.

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?

Input schema coverage is 100%, with descriptions for both 'routerId' and 'name' parameters. The tool description does not add any additional meaning for these parameters; it focuses on output fields. Baseline 3 is appropriate as schema already provides sufficient parameter information.

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 specifies the action 'List' and the resource 'RouterOS scheduler entries' on a MikroTik router. It distinguishes from sibling tools like 'manage_scheduled_job' and other 'list_*' tools by naming 'scheduler entries' and noting key return fields.

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 does not explicitly state when to use this tool versus alternatives. While it's implied this is for read-only viewing and a sibling 'manage_scheduled_job' exists for modifications, no explicit when-to-use or when-not-to-use guidance is provided.

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