marketing_snapshot

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

No annotations provided, so description must disclose all behavioral traits. It states what it returns (GSC totals, top queries, etc.) but does not mention side effects, authentication needs, rate limits, or any cautions. Adequate for a read-only overview but lacks explicit safety or behavior notes.

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?

Concise, front-loaded opener, followed by usage guidance and parameter details. Every sentence adds value; no wasted words.

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?

Output schema exists, so description doesn't need to detail return structure. It lists key data points (GSC totals, top queries, top pages, GA4 engagement, channel breakdown) sufficiently for an overview tool. No missing context for its intended purpose.

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?

Input schema has two parameters (start_date, end_date) with 0% schema description coverage. Description adds format and defaults: 'Start date YYYY-MM-DD (default: 28 days ago)' and 'End date YYYY-MM-DD (default: today)', providing meaning beyond the schema.

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?

Clearly states 'Full marketing overview: GSC organic + GA4 traffic in one call,' specifying the verb (provide overview) and resource (marketing performance combining GSC and GA4). Distinguishes from many sibling tools that focus on individual metrics.

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?

Explicitly says 'Use this as the first tool for any weekly or ad-hoc "give me an overview of marketing performance" question,' providing clear when-to-use context. Lists what it returns, implicitly guiding users to other tools for deeper analysis.

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