analytics_dimensions_details_list

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

Annotations already indicate readOnlyHint=true, so the description only adds the return type information and the important note. It does not disclose other behaviors like pagination or authentication requirements, but annotations cover the safety profile.

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 structured with an Args section and a Returns section, making it easy to parse. However, it is slightly verbose and could be trimmed for 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?

With an output schema present, the description does not need to detail return structure heavily. However, it only vaguely says 'list of all available dimensions with details,' leaving the nature of 'details' unclear. The tool has two simple parameters, so completeness is adequate but not rich.

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 input schema has 0% description coverage. The description mentions `website_id` as a UUID and `dimensions` as a list of dimension names, but this adds minimal meaning beyond the parameter names. It does not provide detailed semantics or formats.

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 'List details of provided dimensions,' specifying the verb (List), resource (dimensions details), and scope (via input). It distinguishes from the sibling `analytics_dimensions_list` which likely lists dimension names only.

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 includes an important usage note about using enum_values object values instead of keys. While it does not explicitly state when to use this tool versus alternatives, the context of the sibling tools and the purpose implies it is for detailed dimension information.

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