getAnalyticsDestinations

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

With no annotations, the description carries the full burden of behavioral disclosure. It only says 'retrieves' without clarifying read-only nature, sorting, pagination, or any side effects. There is no indication of required permissions or what 'most queried' exactly entails (e.g., globally or per 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 a single sentence, which is concise but too sparse. It lacks structure, such as separating purpose from details, and fails to convey important usage information. Every word is used, but the sentence is insufficient for effective tool selection.

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 omits critical context like the meaning of 'most queried' (e.g., time period, popularity metric) and does not mention that the tool returns a list of destinations. For a tool with 5 parameters and 3 required, the description is incomplete.

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 coverage is 100% with descriptions for each parameter. The tool description adds no additional meaning beyond the schema. Baseline is 3 because schema is self-sufficient, but the description does not enhance understanding.

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 states 'Retrieves the most queried destination domains,' which is a clear verb-resource combination. It specifies the object (destination domains) and implies a querying functionality. However, it does not distinguish from similar sibling tools like getAnalyticsDestinationsSeries or getAnalyticsDomains, which might also deal with destination domains.

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. Among many getAnalytics* siblings, there is no differentiation or context on when this tool is appropriate (e.g., for top destinations vs. time series vs. other metrics).

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