list_cron_jobs

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

Without annotations, the description discloses that this is a read operation ('1 RPC read') and describes the output structure (decoded fields, raw object). No side effects or auth requirements are mentioned, but for a read tool this is adequate.

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-loads the action, and includes all essential information without fluff. Every word 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 explains what is returned (decoded fields, raw object) and mentions cost ('1 RPC read'). It lacks details on pagination or result ordering, but for a list tool this is reasonably complete given no output schema.

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 schema has 2 parameters (account, network) with 0% description coverage. The description only implicitly refers to 'account' but does not explain the network parameter or its default. Given low coverage, the description should compensate but does not.

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 lists an account's Cron ledger objects (scheduled Hook self-invocations) and specifies the decoded fields provided. It distinguishes from siblings like build_cronset_unsigned and monitor_cron_health by focusing on listing rather than building or monitoring.

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 indicates this is a read operation ('1 RPC read') and states it lists cron job objects for an account. It does not explicitly exclude alternatives, but the purpose is clear enough that an agent should know when to use it.

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