get_conversions

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

There are no annotations to provide safety or side-effect context, and the description only says 'Get conversion actions and their performance metrics.' It does not disclose behavior such as pagination, default date-range behavior, required permissions, or the shape of returned data. The description carries the full burden but offers very little.

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 concise sentence that front-loads the core purpose. It is efficient, though it could benefit from a brief clarifying clause about how it differs from similar conversion tools without much cost.

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, but the description lacks critical context for a conversion-related tool: it does not state what metrics are included, how the dateRange is defaulted, or what the response contains. With no output schema and no annotations, this leaves the agent uncertain about the tool's exact use case.

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 input schema already provides full documentation for both parameters (customerId and dateRange), including the enum values for dateRange. With 100% schema coverage, the description need not add param details, and it does not, so the baseline score of 3 is appropriate.

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 a specific verb ('Get') and resource ('conversion actions') along with the additional scope of 'performance metrics.' It is understandable and distinct from related conversion tools, though it does not explicitly contrast with siblings like get_conversion_attribution or get_conversion_path_data.

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?

No guidance is provided on when to use this tool versus alternatives. Sibling tools like get_conversion_attribution, get_conversion_path_data, and create_conversion_action handle different aspects of conversions, but the description gives no exclusions or recommended use cases.

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