get_dimensions_by_category

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

The annotations already declare readOnlyHint and idempotentHint, and the description does not contradict them. The description adds a performance note about search_schema being 'faster and more targeted', which provides useful context beyond the annotations. However, it does not describe any additional side effects or requirements like authentication or rate limits, which would have enhanced transparency further.

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 well-structured and concise. It opens with the purpose, then describes the return format, provides usage guidance, and closes with parameter details. Each sentence contributes value without unnecessary fluff, making it easy to parse and act upon.

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 the tool's simplicity (single parameter, no output schema), the description is complete. It covers the return structure, parameter constraints, and alternative tool recommendation, providing sufficient context for an agent to decide when and how to use it. No critical information is missing.

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 schema only defines 'category' as a string, but the description enriches it by specifying that it must be an exact category name from list_dimension_categories and is case-insensitive. This adds crucial semantic detail beyond the schema, ensuring the agent understands the parameter's constraints and origin.

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 that the tool returns all dimensions in a specific category with their API names and descriptions. It distinguishes from the sibling get_metrics_by_category by focusing on dimensions and explicitly mentions an alternative tool (search_schema) for keyword-based searches, making its purpose unambiguous.

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 provides explicit usage guidance: it requires an exact category name from list_dimension_categories and suggests using search_schema instead when a keyword is available, noting it is faster and more targeted. This clearly indicates when to use this tool versus alternatives.

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