get_traffic_sources

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

No annotations are provided, so the description must carry the full burden. It discloses the tool combines three source types and supports filtering, but does not explicitly state it is read-only, nor describe rate limits, pagination, or response structure. While functional, it could add more behavioral context.

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?

Three sentences with no wasted words. The first sentence states the core purpose, the second a usage tip, the third lists filters. Front-loaded and efficient.

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 has 9 parameters and no output schema, the description is fairly complete. It states the output type (sources), suggests usage for comparison, and enumerates filters. It does not describe output format or sorting, but for a data retrieval tool this is acceptable.

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 description coverage is 100%, so the schema already documents all 9 parameters. The description adds value by grouping the filters ('Optional filters segment by...'), but does not provide additional syntax or format details beyond what the schema offers. Baseline 3 is appropriate.

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 it retrieves traffic sources including referrers, trackable links, and UTM campaigns, which is a specific verb-resource combination. It distinguishes from sibling tools like get_analytics (broader) and get_source_conversions (conversion-focused).

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 a concrete usage tip: 'Call twice with different periods to compare source mix over time.' It also lists available filters, giving context on when to use them. However, it does not explicitly state when not to use this tool or mention alternatives like get_source_conversions for conversion data.

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