Delete Managed Object Definition

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

Describes destructive behavior ('deletes', 'removes') and a critical failure condition (reference dependencies). Annotations confirm destructiveHint=true, so description adds specific failure context beyond annotations.

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 concise sentences: first states purpose, second provides essential constraint. No redundant or missing information.

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?

Covers key behavior (delete) and a specific failure scenario. Lacks mention of reversibility or permission requirements, but annotations (destructiveHint, openWorldHint) compensate partially.

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?

Only one parameter (objectName) with 100% schema coverage, including a detailed description. The tool description does not add additional meaning beyond what the schema already provides.

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?

Clear verb ('delete'), specific resource ('managed object type definition'), and context ('from PingOne AIC'). Distinguishes from siblings like deleteManagedObject (deletes instances) and patchManagedObjectDefinition (modifies).

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?

States when not to use due to reference constraints ('fail if other object types have relationship properties referencing this object type'). Implicitly differentiates from deleteManagedObject (deletes instances) and patchManagedObjectDefinition (updates).

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