delete_freeradius_user

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

Annotations already declare destructiveHint=true, and the description adds 'irreversible' which strengthens the warning. However, it fails to mention the confirm flag requirement or dry_run preview capability, both crucial for safe execution of a destructive operation.

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?

Extremely concise single sentence plus warning. Every word contributes to purpose or risk communication; no fluff or repetition.

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?

Tool has 4 params, output schema, and destructive annotations. Description is minimally adequate but omits critical operational context like the need to set confirm=True or use dry_run. Schema covers param semantics, but the description should bridge why those safety gates exist and how they interact.

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 covers 100% of parameters with clear descriptions, including user_id origin and confirm as a safety gate. The description's 'by ID' adds nothing beyond the schema's user_id description, so baseline 3 is appropriate.

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?

Description uses a specific verb 'Delete' with resource 'FreeRADIUS user' and scope 'by ID', clearly distinguishing it from sibling delete_freeradius_client and other delete tools.

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, nor mention of prerequisites like obtaining the user ID via search_freeradius_users. The irreversible warning implies caution but does not provide explicit usage context.

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