ise_openapi_backup_schedule_create

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

No annotations are provided, so the description carries full behavioral disclosure burden. It doesn't state the impact of scheduling a backup, whether this overwrites an existing schedule, whether it requires admin privileges, whether changes are reversible, or what the API response indicates (task ID, success/failure). For a mutation tool (POST) with no annotation coverage, this is a significant gap.

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 that states the purpose and includes the API endpoint. It's efficient with no wasted words. The category tag and endpoint reference are useful context. It could be slightly longer to add behavioral detail, but as written it's concise and front-loaded.

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?

This is a POST (mutation) operation with no annotations, no output schema, and a nested 'data' object. The description provides the API endpoint and category, but fails to explain what the schedule-config-backup body should contain, what the response returns (task tracking via ise_openapi_task_get?), and interactions with sibling backup tools. A mutation tool with no error/return handling context is under-specified.

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 100%, so the schema documents both parameters. The description names the tool's purpose but doesn't elaborate on the 'data' JSON body structure or what fields it requires. The deployment parameter is well-described in the schema including format examples. Baseline 3 is appropriate since the schema does the heavy lifting.

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 it schedules the configuration backup on the ISE node via a POST endpoint. It has specific verb+resource ('Schedules the configuration backup') and category tag [Backup & Restore]. It differentiates from siblings by naming the specific operation (schedule-config-backup) and differs from backup_create, backup_cancel, and backup_schedule_update. However, it doesn't explicitly distinguish from backup_schedule_update, which is closely related.

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 deployment parameter description gives implicit guidance ('Omit to use the only/default deployment. Call ise_list_deployments to see the choices'), which is helpful. However, there's no explicit statement of when to use this tool versus backup_schedule_update or when not to use it. The usage context is implied rather than explicit.

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