semrush_traffic_rank

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the tool is known to be safe and idempotent. The description adds one behavioral context: the need for a '.Trends' subscription. This is useful but minimal beyond what annotations already provide.

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 sentence with no waste, but it is extremely brief. It earns its place but provides too little information to be considered well-structured for a tool with five parameters.

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 five parameters, a required input, and no output schema, the description is critically incomplete. It does not explain what the traffic rank means, how optional parameters affect the result, or what format the output takes. The description fails to provide a usable context.

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%, so the description carries the full burden for explaining parameters. However, it only mentions 'domain' and ignores the other four parameters (country, device_type, display_date, limit). This is insufficient for an agent to use the tool correctly.

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 'Get traffic rank for a domain' which is a specific verb and resource, but among many sibling tools (e.g., semrush_domain_rank, semrush_subdomain_rank), it fails to differentiate what makes this tool distinct. The purpose is clear but not unique.

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. The only extra information is '(requires .Trends)', which is a prerequisite, but it doesn't help an agent decide between this and similar ranking tools.

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