List Scheduled Tasks

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

Annotations already declare readOnlyHint=true, so the description adds no behavioral info. It does not mention the optional parameter include_disabled, sorting, pagination, or any other behavior beyond 'list'.

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 is concise but insufficiently informative. For a tool with one parameter, the description could be expanded without becoming verbose.

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?

Despite having an output schema, the description lacks completeness: it doesn't explain what 'configured' means, whether disabled tasks are included by default, or the effect of the include_disabled parameter. The minimal info leaves gaps.

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 does not explain the only parameter (include_disabled). The parameter name is somewhat self-explanatory, but the agent receives no explicit semantic help.

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 configured scheduled tasks' clearly states the action (list) and the resource (scheduled tasks). The title 'List Scheduled Tasks' reinforces this. It distinguishes from sibling tools like scheduled_tasks_get (single task) and scheduled_tasks_create.

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 list vs. other scheduled task tools (e.g., get, enable). No context about prerequisites or expected use cases. The agent gets no help choosing this tool over siblings.

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