archive_custom_dimension

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

The description adds valuable context by clarifying that custom_dimension_id can be either a numeric ID or a full resource name. It also explicitly signals deletion via '(delete)'. However, no annotations exist, and the description lacks details on permanence, required permissions, or side effects beyond deletion, leaving a transparency gap.

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, front-loaded sentence that immediately states the purpose and then provides a precise parameter detail. Every word earns its place with no redundancy.

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 mutation, the description covers the essential action and a nuanced parameter format. However, it does not mention what happens on success (e.g., return value or irreversible deletion), and given no output schema, this absence leaves the agent uncertain about expected results.

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?

With 0% schema coverage, the description compensates by explaining the acceptable formats for custom_dimension_id. This is critical for correct invocation. The other parameter, property_id, is self-explanatory from its name and context, so partial compensation is sufficient.

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: 'Archive (delete) a custom dimension.' This is a specific verb-resource pair that distinguishes it from sibling tools like archive_audience or create_custom_dimension. The parenthetical '(delete)' reinforces the destructive nature.

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 the tool is used for deleting custom dimensions, but it provides no explicit when-to-use guidance or mention of alternatives. Without a stated exclusion or comparison, an agent must infer usage from the name and sibling context.

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