get_tracking_data

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

No annotations are provided, so the description carries full burden. It describes the tool as getting a 'full activity timeline' but does not disclose behavioral traits like read-only nature, rate limits, or what 'full' entails. The return value is not described, though an output schema exists. Adequate but not rich.

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 a clear purpose sentence followed by parameter documentation. It is efficient but slightly verbose due to including parameter descriptions in the docstring format. No wasted sentences, but could be more concise.

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 absence of annotations and the presence of an output schema, the description covers the essential aspects: purpose, parameter meanings with cross-references to other tools. It does not describe the return format, but the output schema fills that gap. Complete enough for the tool's complexity.

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 description adds significant meaning to each parameter beyond the schema's raw titles. For example, it explains 'website_id' as coming from get_websites and 'session_id' from get_session_ids. Since the input schema has 0% description coverage, the description compensates well.

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 'Get the full activity timeline (user journey) for one session.' The verb 'Get' and specific resource 'activity timeline' make the purpose clear. However, it does not explicitly differentiate from sibling tools like get_session_ids or get_pageview_series, which might also involve session data.

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 implicit usage context by listing parameters with source hints (e.g., 'The website id (from get_websites)'), suggesting a workflow. But it does not explicitly state when to use this tool versus alternatives, nor does it mention prerequisites or exclusions.

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