Dpanel Cron List

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

No annotations are provided, so the description carries the full burden. It implies a read-only listing but says nothing about auth requirements, pagination, filtering behavior, or scope (all tasks vs. project-scoped). For a zero-annotation tool this is thin, though the low-risk nature of a list limits the harm.

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?

It is a single short phrase with no waste and the purpose is front-loaded, but this is under-specification rather than effective conciseness — the brevity leaves real gaps an agent must guess at.

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?

An output schema exists so return values need not be explained, and there are no parameters to document. However, with eight sibling cron tools, the description gives no scope, ordering, or relationship context, leaving the agent unable to confidently route between this and dpanel_cron_detail.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate. Baseline 4 applies; no parameter semantics are missing.

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?

"计划任务列表" states a resource (scheduled tasks) and implies the list operation, but it essentially restates the tool name (dpanel_cron_list) without distinguishing it from siblings like dpanel_cron_detail or dpanel_cron_log_list. An agent can infer the basic purpose but gets no scope detail.

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 when-to-use guidance, no exclusions, and no mention of alternatives such as dpanel_cron_detail for a single task. The agent must infer that this is the browse-all entry point purely from the name.

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