reports_series_dimensions

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

The description explains that the output is meant for the 'by' parameter, which adds useful behavioral context. However, with no annotations, it doesn't explicitly state whether this is a read-only operation or other side effects, though the 'list' verb implies it.

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?

Two concise sentences front-load the action and immediately state the purpose. No filler or redundant information.

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 zero-parameter list tool with an output schema, the description is complete. It states what is listed and how the list is used, while the output schema handles return format details.

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 tool accepts zero parameters, so the baseline is 4. The description further adds meaning by explaining that the returned dimensions are values for the 'by' parameter in reports_series, which provides context beyond the empty schema.

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 tool lists dimensions for reports_series, with an explicit link to the 'by' parameter. This distinguishes it from other list tools like list_sub_accounts or list_users, making the purpose immediately understandable.

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?

It explicitly says when to use this tool (to get valid values for the 'by' parameter of reports_series). It doesn't mention exclusions or alternatives, but the usage context is clear enough for such a simple metadata tool.

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