agency-hosting_createAgencyPlanWebsiteCronJobV1

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

With no annotations, the description carries full burden. It discloses that the tool returns the created cron job including its uuid for deletion, which is a behavioral trait. However, it lacks details on side effects, permissions, or constraints beyond the schema's restrictions on the command parameter.

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 long, front-loaded with the main action, and every word serves a purpose. No unnecessary information.

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?

Given no output schema, the description adequately explains the return value (uuid for deletion). For a simple CRUD creation tool, it covers the essentials, though it omits details like validation of the schedule expression or the command restrictions, which are in the 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 input schema already provides 100% coverage with descriptions for all three parameters. The description loosely references 'schedule expression and a command' but does not add new meaning beyond the schema's parameter descriptions.

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 verb 'Creates' and the resource 'cron job for an Agency Plan website', with the inputs 'schedule expression and a command'. It distinguishes itself from sibling tools like delete and list by specifying the creation action and the returned uuid needed for deletion.

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 implicitly guides usage by stating that the returned uuid is required to delete the cron job, indicating a lifecycle. However, it does not explicitly provide when-to-use or when-not-to-use contexts compared to alternatives like listing or deleting cron jobs.

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