List Agency Cron Jobs

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

With no annotations, the description carries the full burden of behavioral disclosure. It only says 'List', implying a read-only operation, but does not mention authorization needs, pagination, response format, or any side effects. This is a significant gap even for a simple list tool.

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 concise sentence with no superfluous words, making it efficient. However, it is so minimal that it could include additional useful context (e.g., alternative tools) without becoming verbose, so a perfect score is not warranted.

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 list operation, the description is minimally adequate. However, with no output schema and no annotations, it does not explain the return format or any caveats. Given the presence of a closely related sibling tool (hosting_cron_list), a bit more contextual information would improve completeness.

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 fully describes the single required parameter 'website_uid' with a clear description. The tool description adds no additional meaning to this parameter, so the baseline of 3 for high schema coverage is appropriate.

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 action (List), the resource (cron jobs), and the scope (Agency Plan website), making its purpose unambiguous. The explicit 'Agency Plan website' qualifier helps distinguish it from the similar hosting_cron_list sibling.

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 is provided on when to use this tool versus alternatives like hosting_cron_list or agency_cron_create. There is no mention of prerequisites, exclusions, or context clues beyond the implicit Agency Plan scope, leaving the agent to infer.

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