ga4_get_conversions

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

No annotations are provided, so the description is the only source of behavioral info. It clearly describes the output (counts, event names) and the default lookback period, and explains that property_id can fall back to an environment variable. It does not mention any side effects, rate limits, or required permissions, but for a read-oriented tool this description is reasonably transparent.

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 concise and well-structured: a one-sentence summary, a brief explanation, and a clear Args list. Every sentence adds value, and the format makes it easy to parse.

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?

The tool is simple with three parameters, and the description covers its purpose, output, and parameter semantics. The output schema exists so return format isn't needed. The only gap is the lack of explicit mention of required permissions or usage context relative to siblings, but this is not critical for invocation.

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 Args section explains each parameter's meaning (property_id with env var fallback, days as lookback, row_limit as max rows) and provides defaults. This goes well beyond the input schema, which only lists types and defaults, and provides valuable context for correct invocation.

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's function: 'Get conversion events and their counts' and explains the breakdown by event name. This specific verb and resource clearly distinguishes it from sibling tools like ga4_get_top_pages or ga4_get_traffic_sources.

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 implies the tool should be used when conversion event data is needed, but it does not explicitly state when to use this versus alternatives. There is no mention of exclusions or comparisons to sibling tools, so the agent must infer usage from the tool's name and description.

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