create_backup

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states 'Create a configuration backup' which implies a write operation, but does not cover critical aspects such as permissions required, whether it's idempotent, rate limits, what happens if a backup already exists, or the format/scope of the backup. This leaves significant gaps for an agent to understand the tool's behavior.

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 extremely concise with just three words ('Create a configuration backup'), front-loaded with the core action, and contains no unnecessary information. It efficiently communicates the essence of the tool without waste.

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 a backup creation tool (a write operation with potential side effects), no annotations, and no output schema, the description is insufficient. It lacks details on what the backup entails, how to verify success, error handling, or interaction with sibling tools, making it incomplete for safe and effective use by an agent.

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 100% description coverage for its single parameter ('description'), so the schema already documents it adequately. The description does not add any additional meaning or context about the parameter beyond what the schema provides, such as examples or constraints, but this is acceptable given the high schema coverage.

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 'Create a configuration backup' clearly states the action (create) and resource (configuration backup), making the purpose understandable. However, it does not differentiate from sibling tools like 'list_backups' or 'restore_backup', which would require more specificity about what type of backup or context.

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 provides no guidance on when to use this tool versus alternatives like 'list_backups' or 'restore_backup', nor does it mention prerequisites, dependencies, or typical use cases. It simply states what the tool does without contextual usage information.

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