wordpress_schedule_backups

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

No annotations are provided, so the description must fully disclose behavioral traits. 'Schedule automatic backups' implies a write/mutation operation (scheduling), but it doesn't specify permissions required, whether it overwrites existing schedules, rate limits, or what happens upon invocation (e.g., immediate backup or future trigger). This leaves critical behavioral aspects unclear.

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, efficient phrase ('Schedule automatic backups') with no wasted words. It's front-loaded and appropriately sized for a tool with no parameters, making it easy to parse quickly.

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 the complexity of scheduling backups (a mutation tool with no annotations or output schema), the description is insufficient. It lacks details on what is backed up, scheduling options, behavioral outcomes, or how it differs from sibling backup tools. This leaves significant gaps for an agent to understand and use the tool effectively.

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 has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate. A baseline of 4 is applied as it compensates adequately for the lack of parameters.

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 'Schedule automatic backups' clearly states the verb ('Schedule') and resource ('automatic backups'), but it's vague about what exactly is being scheduled (e.g., database, files, full site) and doesn't distinguish from siblings like 'wordpress_backup_database', 'wordpress_backup_files', or 'wordpress_full_backup'. It provides a basic purpose but lacks specificity.

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 offers no guidance on when to use this tool versus alternatives like 'wordpress_backup_database' or 'wordpress_full_backup'. It doesn't mention prerequisites, frequency settings, or any context for scheduling. Without such details, the agent has little basis for choosing this tool over others.

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