semrush_traffic_destinations

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, establishing the tool as a safe read operation. The description adds the behavioral note about requiring '.Trends', which is useful context beyond annotations. However, it does not describe output format, pagination, or other behavioral traits, so value added is limited.

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, efficient sentence that front-loads the core action. It is not verbose, but it omits critical parameter details, which could be added without sacrificing conciseness. It earns its keep by stating the prerequisite.

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 5 parameters with 0% schema description coverage and no output schema, the description is too sparse. It lacks information on parameter format, valid values, and expected return structure, making it difficult for an agent to use correctly. Annotations provide safety context, but completeness is low.

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 must compensate for parameter meaning. The description only implies 'target' is a domain but provides no explanation for 'country', 'device_type', 'display_date', or 'limit'. Without schema descriptions or additional context, the agent has insufficient semantic understanding to correctly invoke parameters.

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 uses a specific verb 'Get' and resource 'outbound traffic destinations', clarifying the tool's function. It includes a prerequisite ('requires .Trends'), which adds clarity. However, it does not explicitly differentiate from sibling tools with similar names like traffic_sources or traffic_geo, though the term 'destinations' provides some distinction.

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 the requirement '.Trends', indicating a condition for use. However, it does not provide guidance on when to use this tool versus alternatives among the many sibling traffic tools (e.g., traffic_sources, traffic_summary), leaving the agent to infer based on the tool name alone.

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