neuron_schedule_list

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

No annotations are provided, so the description carries the behavioral disclosure burden. 'List all scheduled recipes...' signals a read-only operation and discloses the output attributes, but it adds no deeper context such as auth requirements, behavior with no schedules, ordering, or pagination. The basic behavior is clear, but there is room for more transparency.

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 a single front-loaded sentence that names the action, scope, and the key output fields with no filler. Every element contributes to understanding the tool's purpose.

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?

For a simple zero-parameter read-only list tool with no output schema, the description gives the core return palette, so an agent knows what to expect. It stops short of specifying the exact response shape, ordering, or default behavior when no schedules exist, but these are not critical for selection or invocation.

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 has zero parameters and the schema is 100% covered, so the description needs to add no parameter detail. With no parameters, the baseline is 4; the description accurately focuses on output, which is the only relevant invocation consideration.

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 uses a specific verb ('List') with a clear resource ('scheduled recipes') and enumerates the return fields ('next run time, last run time, run count, and enabled status'). This makes it easily distinguishable from sibling tools like neuron_recipe_list (all recipes) and neuron_schedule_toggle/recipe (schedule management), not just a restatement of the name.

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 the use case: retrieve all scheduled recipes when you need scheduling status and timing. However, it gives no explicit guidance about when not to use it, and it does not name alternatives such as neuron_schedule_recipe, neuron_schedule_toggle, or neuron_recipe_list for recipe management scenarios.

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