get_link_analytics

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

No annotations are provided, so the description must fully convey behavioral traits. It discloses the output structure (clicks, time series, breakdowns) and the effect of the days parameter. However, it does not mention error handling, caching, or data freshness, which are important for an analytics tool.

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 sentences precisely convey purpose and key parameter usage without unnecessary words. The description is front-loaded with the main action and then details output and parameter control.

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 no output schema, the description lists the main analytics components (total clicks, unique clicks, time series, breakdowns) which provides a solid understanding of the response. It is adequate but could mention error responses or response format for completeness.

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%, and the description adds minimal value beyond the schema for 'days' (repeating the default) and nothing for 'linkId.' The baseline of 3 is appropriate as the description does not enhance parameter 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 clearly states 'Get detailed analytics for a single deep link.' This is a specific verb (Get) and resource (analytics for a single deep link), which distinguishes it from sibling tools like get_overview_analytics (workspace-level) and get_funnel (funnel-specific).

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 implicitly suggests use for a single deep link by naming the resource, and it explains the days parameter usage. However, it does not explicitly compare with siblings or state when not to use this tool, so it falls short of a 5.

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