schedule_list

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

The description mentions OS coverage (Windows, macOS, Linux) and namespace, but lacks details on return format, performance, permissions, or error conditions. Since no annotations are provided, the description should carry more behavioral context.

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?

The description is two sentences, front-loaded with the main action, and contains no extraneous words. Every sentence 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?

The description covers the tool's scope and OS support, but lacks output format details. Since there is no output schema, the description should at least hint at what a task object contains (e.g., name, trigger).

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?

Tool has no parameters (0 params, 100% schema coverage), so baseline is 4. The description does not need to add parameter details, but it could mention that no arguments are required.

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 specifies 'List all SCOUT scheduled tasks on this machine', clearly stating the verb (list), resource (SCOUT scheduled tasks), and scope (on this machine). It also distinguishes from siblings schedule_create and schedule_delete by focusing on listing only.

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 implies this tool is for viewing existing tasks, and siblings are for create/delete. However, it does not explicitly state when to use this tool versus alternatives, leaving it implicit.

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