Get Conversion Actions

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

With no annotations provided, the description carries the full burden. It says 'List' which implies a read-only operation, but it doesn't disclose what the output includes, whether it's paginated, if it requires manager_id under managed access, or any rate or size constraints. The schema hints at optional manager_id but the description adds nothing beyond 'list'.

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 a single short sentence, front-loading the key verb and resource. No waste, though it could add one clause about scope or usage without losing concision.

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 an output schema (presumably listing available conversion actions), the return format isn't needed. However, with no annotations and no usage context among many siblings, the description lacks complete context about when to fetch conversion actions, e.g., for referencing conversion actions in other reports or for setup. It's minimal but not wholly inadequate.

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 both parameters. The description adds no further meaning about how customer_id or manager_id interplay or what happens if manager_id is omitted. Baseline 3 is appropriate since schema handles semantics.

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 verb 'List' and the resource 'conversion actions' with scope 'on the account'. This is clear and distinguishes it from performance-focused siblings, though it doesn't explicitly name a difference from a hypothetical other conversion-action tool.

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 gives no guidance on when to use this tool versus the many siblings. It only says 'on the account', which implies account-level scope but offers no exclusion or comparison, such as when to use run_gaql for custom queries.

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