pbs_group_change_owner

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

Discloses mutation nature, dry-run default, immediate loss of permissions, and reversibility. No annotations provided, so description carries the burden effectively.

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?

Concise at 7 lines, front-loads purpose and effects. Includes the HTTP path line, which is slightly extraneous but not overly verbose.

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?

Covers key behavioral aspects (dry-run, effects, reversibility) and hints at API path. Missing permissions, side effects on backups, and clarification of backup_type/backup_id identifiers.

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 coverage is only 14%, but description adds little to parameter meaning. Only 'confirm' and 'new_owner' get brief mentions; 'store', 'backup_type', 'backup_id', 'ns', and 'proximo_target' remain unexplained.

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?

Clearly states the action ('reassign the owner') and the resource ('PBS backup group'). No sibling tool performs owner change, so it is distinct.

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?

Explains default dry-run and how to execute ('confirm=True'), and describes effects (new owner gains control, previous loses immediately). Lacks explicit when-not-to-use or prerequisites.

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