semrush_purchase_conversion

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds behavioral context beyond annotations by specifying the subscription requirement (.Trends) and platform limitation (desktop only). However, it does not discuss rate limits, data freshness, or output format.

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, front-loaded sentence of 13 words that immediately conveys the core purpose. It contains no unnecessary information, making it highly efficient for an agent 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?

Given the tool has no output schema and four parameters (with zero schema description), the description does not cover what the tool returns (e.g., single value, time series) or explain parameters like 'display_date' and 'limit'. The lack of output details and parameter semantics leaves significant gaps for an agent to correctly invoke the tool.

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 0%, meaning no parameter descriptions in the schema. The description fails to compensate by explaining any of the four parameters (target, country, display_date, limit) beyond implying 'target' is the domain. This leaves the agent without necessary usage details for parameters like 'country' or 'limit'.

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 verb 'Get', the resource 'purchase conversion rate', and the scope 'for a domain', distinguishing it from other domain metric tools like traffic or backlinks. The constraints (requires .Trends, desktop only) further clarify its purpose.

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 mentions prerequisites (requires .Trends, desktop only) but does not provide guidance on when to use this tool versus the many sibling tools for other domain metrics. No explicit when-to-use or when-not-to-use advice is given.

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