create_custom_dimension

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only states 'create' implying a mutation, but lacks details about side effects, required permissions, rate limits, or what the output schema contains. Minimal 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 short (five words), but this brevity comes at the cost of essential information. It is an under-specification rather than a model of conciseness. The structure is flat with no front-loading of key details.

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?

Given 5 parameters with 0% schema coverage, no annotations, and an output schema that is not mentioned, the description is thoroughly incomplete. It fails to provide necessary context for an AI agent to understand the tool's behavior, parameters, or output.

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?

Schema description coverage is 0%, meaning the input schema has no parameter descriptions. The description adds no information about the five parameters (including required ones like property_id, parameter_name, display_name) or their semantics. This is a critical gap.

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 'Create a custom dimension' clearly states the action (create) and resource (custom dimension). However, it does not distinguish this tool from sibling tools like create_custom_metric, which also creates a custom entity. A score of 4 reflects clarity without sibling differentiation.

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?

No guidance is provided on when to use this tool versus alternatives such as create_custom_metric or create_key_event. There are no prerequisites, context for appropriate usage, or exclusions. The description gives no usage direction.

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