archive_custom_dimension

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states 'Archive (delete)', which indicates a destructive operation, but does not mention whether the action is reversible, what side effects occur (e.g., on reports or metrics), or any permission requirements. This is a significant gap for a deletion tool.

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 sentence with no redundant wording. It front-loads the action and immediately addresses a likely parameter confusion. This is appropriately concise for a simple tool.

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 two-parameter destructive tool with no output schema and no annotations, the description provides the core action and an important parameter detail, but it omits consequences (e.g., permanence, permission needs) and return behavior. It is minimally complete but leaves the agent guessing about the full impact.

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 description adds useful semantics for custom_dimension_id by clarifying it can be a numeric id or full resource name, which is beyond the bare schema. However, property_id lacks any explanation, and with 0% schema description coverage, the description only partially compensates for the two parameters.

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)' and the resource 'custom dimension', making the tool's purpose obvious. It does not explicitly differentiate from sibling tools like archive_audience, but the resource specificity is sufficient. A score of 5 would require explicit mention of alternatives or scope exclusions.

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 provides no guidance on when to use this tool versus alternatives, nor does it list any prerequisites or exclusions. Usage is only implied by the action itself, which is insufficient for a tool with many siblings like create_custom_dimension and list_custom_dimensions.

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