Update backup schedule

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

Annotations already provide idempotentHint=true and destructiveHint=false. The description adds no behavioral context beyond 'update', such as what parts of the job are modified, whether changes are incremental, or any required permissions. With annotations present, the description should augment them, but it does not.

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 sentence of 7 words, very concise. However, it is too sparse and sacrifices valuable information for brevity. It could include a brief note on common use cases or parameter groups.

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 tool's complexity (23 parameters, no output schema, numerous siblings), the description is extremely incomplete. It fails to mention that it's for Proxmox VE backup jobs, that it requires an existing job ID, or what ranges of updates are supported. The sibling list includes many update tools, so differentiation is critical but missing.

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?

Schema description coverage is only 4%, meaning almost no parameter descriptions in the schema. The description 'Update an existing scheduled backup job' provides zero parameter information. It does not explain any of the 23 parameters (e.g., mode, pool, schedule) or their semantics.

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 'Update an existing scheduled backup job' clearly states the verb (Update) and resource (existing scheduled backup job). It distinguishes from create/delete siblings, but the title 'Update backup schedule' could mislead by implying only schedule changes, while the schema includes many other parameters.

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 on when to use this tool versus alternatives like create_backup_job or update_container_config. No prerequisites or exclusions mentioned. The description provides no context for decision-making.

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