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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered and 'Read only' is largely redundant. The description does add scope value by enumerating what data is surfaced (tag detection, weekly events, pixel/platforms, Stripe) and noting money is in minor units. It stops short of describing freshness, pagination, or how the platform/Stripe checks are performed.

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?

A single sentence with no wasted preamble, front-loaded with 'Sales tracking' and closed with the read-only marker. The comma-separated list is a bit dense and slightly cryptic in places ('other platforms it sends to'), but overall it earns its length.

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 has no inputs, full annotation coverage, and an output schema, so the description need not explain return structure or safety. It adequately scopes the data domain; the only meaningful gap is routing guidance against sibling reporting tools, which is a usage concern rather than a completeness one.

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 tool takes zero parameters, so there is nothing for the schema to describe and the baseline of 4 applies. The description's detail about data scope and the 'minor units' convention adds useful interpretive context even though no parameters exist.

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 is a noun-phrase list of data points (Siren tag, events this week, Meta pixel, Stripe, 30-day revenue) prefixed by 'Sales tracking,' rather than a clean verb+resource statement. An agent can infer it retrieves conversion-tracking status, but the actual operation is never stated outright. It also does not explicitly distinguish itself from sibling reporting tools like ad_performance or get_performance.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives. With reporting siblings such as ad_performance, get_performance, and ads_overview present, the agent is left to guess which tool answers a conversion-tracking question. Only the 'Read only' tag hints at usage context.

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