sophos_delete_all_mdr_threat_feed_indicators

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

With no annotations, the description carries the full burden. It clearly labels the operation as destructive and irreversible ('no undo'), which is critical transparency. However, it could mention additional behavioral traits such as impacts on firewall blocking or required permissions.

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?

Two sentences: first states the action, second warns about destructiveness. No extraneous words; information is front-loaded and efficient.

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 full schema coverage and no output schema, the description covers the core purpose and a key warning. It is complete for a bulk delete tool, though it could note the bulk nature more explicitly (already implied by 'ALL') or mention that the feed becomes empty.

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 descriptions for both parameters ('Tenant UUID', 'Firewall UUID'). The description does not add any further meaning beyond the schema, 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?

The description clearly states 'Delete ALL threat indicators from a firewall's MDR threat feed.' It specifies the verb (Delete), resource (threat indicators from a firewall's MDR threat feed), and scope (ALL). It distinguishes from sibling tools like sophos_delete_mdr_threat_feed_indicators (which likely deletes specific indicators) by emphasizing 'ALL'.

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 warns 'This is a destructive operation with no undo,' but does not explicitly state when to use this tool versus alternatives (e.g., sophos_delete_mdr_threat_feed_indicators for selective deletion). It lacks context on when not to use it or when another tool is preferred.

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