delete_service_lines_by_service_line_number

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

Annotations already indicate destructive behavior. The description adds the required permission and HTTP method, which is useful but does not explain what 'deactivate' entails (e.g., soft delete, impact on subscriptions) beyond the 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?

The description is extremely concise: a single sentence with key details (action, permission, HTTP method). It is front-loaded and contains no filler content.

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?

Despite having 3 parameters and a destructive effect, the description does not address behavior for optional parameters (reasonForCancellation, endNow) or what happens after deactivation. The lack of output schema means more context would be helpful, but it is not provided.

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 provides complete descriptions for all parameters (100% coverage). The description does not add any additional meaning or context for the parameters, so baseline score applies.

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 explicitly states 'Deactivate a service line,' specifying the verb and resource. It clearly distinguishes from sibling delete tools that operate on different entities (e.g., contacts, routers configs).

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 only mentions required permissions. It provides no guidance on when to use this tool versus alternatives like other service line tools (e.g., patch, post) or related delete tools.

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