list_custom_dimensions

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

The description lacks behavioral details beyond the basic action. It does not disclose that this is a read-only operation, nor does it mention pagination, sorting, filtering, or authorization requirements. With no annotations, the description carries the full burden, and it falls short.

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 waste. It is front-loaded with the action and resource. However, it is too brief to be considered ideal; a bit more structure (e.g., listing key details) would make it more helpful without harming conciseness.

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?

Despite having an output schema, the description does not hint at return values or structure. For a simple list tool, the agent would benefit from knowing what fields are returned or that it returns an array of custom dimension objects. The description is incomplete for practical use.

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%, and the description provides no additional meaning for the single parameter 'property_id'. The agent is left without any hint about what value to provide or how to obtain it. The description adds no value beyond the schema's technical definition.

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 (list) and resource (custom dimensions) scoped to a property. However, it does not differentiate from sibling tool 'list_custom_metrics', which has a similar structure and scope. A more specific description would include that it lists dimension definitions specifically, but it's still clear enough.

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 like 'create_custom_dimension' or 'list_custom_metrics'. There is no mention of prerequisites, context, or situations to avoid. This leaves the agent to infer usage from the name alone.

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