List conversion trackers

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds only 'of the account' as scope context and says nothing about pagination, result limits, or how the optional status filter affects results, so it contributes very little behaviorally.

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?

At six words it is short, but this is under-specification rather than conciseness: it is a sentence fragment with no actionable content front-loaded beyond the resource name. Every word earns little because no real information is conveyed.

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?

For a low-complexity list tool with no output schema, the description still omits the one parameter's purpose, expected return shape, and relationship to sibling tools. An agent would have to guess what a 'conversion tracker' is and whether filtering is needed.

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 single parameter (status, enum active/paused) has 0% schema description coverage, so the description carries the burden of explaining it — but the status filter is never mentioned. The description adds no meaning beyond the schema's enum values.

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 states the resource (S2S conversion trackers) and scopes it to the account, but it is a bare noun phrase with no verb and the 'S2S' jargon is never expanded. The verb 'list' must be inferred from the tool name, and nothing distinguishes it from the sibling get_conversion_tracker or list_conversion_events beyond plurality.

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 guidance on when to use this list tool versus get_conversion_tracker (single) or list_conversion_events, nor any mention of prerequisites or context. Usage is only implied by the name.

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