Delete Journey

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

Annotations already mark destructiveHint=true, but the description adds value by detailing that AM automatically cleans up all node instances, including PageNode child nodes. This goes beyond simple write behavior and provides essential context about cascading effects. No contradictions with 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 sentences with no filler: first sentence states the core purpose, second adds critical behavioral detail. Every word earns its place, and the structure is front-loaded.

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?

For a simple delete tool with two parameters, no output schema, and annotations covering destructive nature, the description is fully complete. It covers purpose, scope, automatic side effects, and the realm/journey identification context is clear from the schema.

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?

Both parameters (realm, journeyName) are fully described in the input schema (100% coverage). The description does not add additional meaning or constraints for these parameters beyond what the schema provides, 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 uses a specific verb ('Delete') and resource ('authentication journey from a realm') clearly distinguishing it from sibling tools like deleteJourneyNodes (which only removes nodes) or deleteManagedObject. The addition of automatic cleanup of node instances further clarifies scope.

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 implicitly states when to use this tool (when you want to delete a journey) but does not explicitly mention when not to use it or alternatives. However, the context of automatic cleanup provides useful guidance on what happens during deletion, making the usage clear enough for an agent.

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