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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is known. The description adds value by explaining a non-obvious side effect: the removed list also removes its 'reusable segment boundary.' This is meaningful behavioral context beyond the annotations, though it does not detail irreversibility or cascading effects.

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 a single, concise sentence with no filler. Both clauses carry important information: the core action and the segment boundary side effect. It is appropriately front-loaded and every word earns its place.

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 one-parameter delete operation with strong annotations (destructive, idempotent) and no output schema, the description provides the essential behavioral nuance (segment boundary removal) and relies on schema for parameter semantics. It is complete enough, though it could mention permanence or behavior on non-existent lists, but idempotentHint mitigates that concern.

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 fully describes the single parameter listId as 'The unique identifier of the company list to delete' (100% coverage). The description does not add any additional parameter meaning, so it relies on the schema. The baseline of 3 applies here.

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 ('Delete') and resource ('saved company list'), and adds a specific consequence ('remove its reusable segment boundary'). This distinguishes it from other list operations like company_lists-get or company_lists-update, and clearly identifies the domain (company lists vs. contact lists).

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 implies usage: it is the tool for deleting saved company lists. However, it does not explicitly state when to use this over alternatives (e.g., contact_lists-delete) or mention any prerequisites or exclusions. The context of the tool name and sibling set makes the usage clear, but explicit guidance is lacking.

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