ad_manager_google_delete_segment

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

The annotations declare destructiveHint=true, which matches the 'Delete' action, so there is no contradiction. However, the description adds no context about what happens when a segment is deleted, whether deletion is reversible, required permissions, or side effects. With annotations already covering destructiveness, the description offers no additional behavioral transparency.

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 (two words), but it is under-specified and fails to provide useful context. It reads more like a placeholder than a helpful description, so it is not appropriately sized for an agent that needs to understand the tool's behavior.

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?

There is no output schema, and the description gives no context about the segment types, the meaning of locationId, or any prerequisites. Given that this is a destructive operation and there are sibling tools for creating and retrieving segments, the description is inadequate to guide an agent on correct usage.

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 schema covers 100% of the parameters with descriptions, so the baseline is 3 even without parameter info in the tool description. The description itself does not mention parameters or add any meaning beyond what the schema already provides, so it stays at the baseline.

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 'Delete segment' states a verb and resource, but it is essentially a restatement of the tool name. It does not specify that it operates on Google Ad Manager segments, nor does it distinguish between custom and data segments, which are the two enum options for the 'type' parameter. No additional specificity is provided beyond the name.

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?

There is no guidance on when to use this tool versus alternatives like ad_manager_google_upsert_segment or ad_manager_google_get_segments. No conditions, prerequisites, or context for selecting segment type are provided. The description is completely silent on usage.

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