create_custom_dimension

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

With no annotations, the description should disclose side effects, prerequisites, and result behavior. It only explains parameter semantics and validation rules, not what happens on creation (e.g., idempotency, error cases, permissions). This leaves a significant transparency gap for a mutation 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 brief and front-loaded with the core action. It uses a single sentence plus a few clarifying notes, with no wasted words.

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?

The tool has no annotations and no output schema, and the description does not explain all required parameters (property_id) or mention what a successful creation returns. Given the complexity of five parameters and a create operation, the description is insufficient for confident use without external knowledge.

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 explains the meaning of parameter_name, scope, and display_name constraints, which adds value beyond the schema (0% coverage). However, it leaves property_id and the description parameter unexplained, so not all parameters are semantically covered.

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 'Create a custom dimension' with a specific resource, distinguishing it from sibling tools like create_custom_metric. It also provides immediate clarity on key parameters.

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 when to use this tool (when a new custom dimension is needed) but does not explicitly mention alternatives or exclusions, such as contrasting with create_custom_metric or noting that list/archive operations are separate.

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