sophos_delete_tenant_role

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only mentions that built-in roles cannot be deleted, but omits important traits such as whether deletion is reversible, what happens to associated role assignments, required permissions, or potential error conditions. This is insufficient for a mutation tool.

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, consisting of two sentences that convey the core purpose and a critical constraint without any unnecessary words. Every sentence adds value.

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 absence of annotations and output schema, the description provides adequate context for the deletion operation and the key constraint. However, it lacks details about return values, error handling (e.g., if role is built-in or not found), and side effects, which an agent might need for robust invocation.

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 with clear parameter descriptions. The tool description adds no additional meaning beyond what the schema already provides, so a baseline score of 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?

The description clearly states 'Delete a custom role from a tenant.', specifying the action (delete) and the resource (custom role). It also distinguishes from other delete tools by noting that built-in roles cannot be deleted, which differentiates it from siblings like sophos_delete_tenant or sophos_delete_tenant_admin.

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 explicitly states when to use the tool (for custom roles) and provides a clear exclusion (built-in roles cannot be deleted), guiding the agent not to attempt deletion of built-in roles. However, it lacks explicit guidance on alternatives or prerequisites, such as suggesting checking role type via sophos_get_tenant_role or noting required permissions.

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