sophos_delete_cloud_security_profiles

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

Given no annotations, the description adequately discloses critical behavioral traits: the destructive nature (deletion), the partial failure condition (profiles assigned to policies), and the inclusion of a 'skippedProfiles' list. It does not cover authorization needs or rate limits, but the transparency is high for a delete 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?

The description is two sentences with no wasted words. It immediately states the purpose and then adds a critical behavioral caveat. Perfectly front-loaded and concise.

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?

With no output schema, the description hints at the response structure via 'skippedProfiles', which is helpful. However, it does not fully describe the response (e.g., success indicators, error details for failed deletions). It covers the essential context for a delete tool but could be more complete.

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 100% with clear descriptions for both parameters. The description adds no additional meaning beyond the schema; it only repeats the method of deletion by IDs. The mention of 'skippedProfiles' is about response behavior, not parameter semantics. 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?

The description clearly states the verb 'Delete' and the resource 'cloud security runtime detection profiles' with the method 'by their IDs'. This distinguishes it from other delete tools for different resources (e.g., sophos_delete_policy) and from the create/get/list/update variants for cloud security profiles.

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 useful guidance by stating that profiles assigned to a policy cannot be deleted and will be listed in 'skippedProfiles'. However, it does not explicitly mention when to use this tool vs alternatives (e.g., unassigning profiles first) or compare with other delete tools.

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