list_all_scheduled_actions

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

Given no annotations, the description compensates well by disclosing pagination behavior, filter exact-match nature, and limit cap. It avoids contradictions and adds value beyond defaults.

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?

Extremely concise: three sentences front-loading the core action, then detailing parameters and behavior with no unnecessary words.

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?

Covers essential aspects (pagination, filters, defaults) for a list operation. Output schema is present, so return values are implicit. Minor gap: no mention of error conditions or rate limits.

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?

With 0% schema description coverage, the description adds meaning to all parameters: explains usage of limit, offset, exact-match filters for action_types and scheduler, and suggests values from meta fields.

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 states the tool queries scheduled actions, effectively communicating the verb-resource relationship. It distinguishes itself from sibling tools that focus on systems and updates.

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?

Provides guidance on optional filters and pagination (limit capped at 500, use meta.next_offset). However, it does not explicitly state when not to use this tool or compare to alternatives.

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