cipp_delete_standard_template

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

Beyond the annotation destructiveHint=true, the description adds critical behavioral details: the deletion is permanent, and tenants assigned to the template will lose the enforced standards. This provides transparent effect of the 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 very concise with two short sentences. It front-loads the critical warning 'HIGH-IMPACT' and states the purpose, effect, and required user confirmation without any fluff.

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 one required parameter and no output schema, the description fully explains what the tool does, its impact, and the consequence for assigned tenants. There is no missing information for an agent to decide to invoke it.

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 already describes the only parameter templateId as a GUID. The description does not add additional meaning or examples, so it provides no extra value beyond the schema. Schema coverage is 100%, 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 action (permanently deletes) and the resource (CIPP Standards Template by ID). It distinguishes from sibling tools like cipp_create_standard_template and cipp_list_standard_templates by specifying the verb 'delete' and the scope 'by ID'.

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 includes a strong usage caveat: 'HIGH-IMPACT' and 'Confirm with the user before invoking', guiding the agent to use only after user confirmation. However, it does not explicitly state when not to use or provide alternatives to deletion.

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