delete-service

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

With no annotations, the description carries the full burden and does well: it explicitly flags 'WRITE OPERATION: changes PCE state' and explains the approval-pause behavior in gating clients, including that the call has not failed and must not be retried. This is valuable behavioral disclosure beyond the bare delete action, though it does not mention irreversibility or permission requirements.

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 compact and front-loaded: purpose first, then state-change warning, then approval-pause guidance. Every sentence adds distinct value with no wasted words.

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 two-parameter delete tool without an output schema, the description covers the essential operational context: the write side effect, the approval delay, and identifier selection. It could explicitly state that at least one of href or name is required, but this is reasonably implied and not a major gap.

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 description coverage is 100%, so the schema already documents href and name. The description adds only a preference hint ('href preferred') without new semantic detail, so the baseline of 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 opens with a specific verb and resource: 'Delete a service from the PCE.' This clearly distinguishes it from sibling tools like delete-workload, delete-iplist, or delete-ruleset. The resource scope (PCE service) is unambiguous.

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 gives parameter-usage guidance ('Identify by href (preferred) or name') but does not explicitly state when to use this tool versus alternatives like delete-workload or delete-sec-rule. The context is implied by the tool name and resource, but no exclusions or sibling comparisons are provided.

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