semrush_traffic_subdomains

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

The description adds the '.Trends' requirement, which is a behavioral constraint beyond the annotations (readOnly, idempotent). However, it does not disclose other behaviors like rate limits, error cases, or what happens with invalid targets. Given annotations already cover safety, this is adequate but not rich.

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 starting with the verb 'Get,' making it front-loaded and efficient. However, it may be too terse given the lack of parameter documentation, but conciseness itself is a strength.

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 (including an enum) and no output schema, the description is far from complete. It does not explain the output format, how parameters affect results, or any constraints. The agent would struggle to use this tool effectively without external documentation.

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% (no parameter descriptions in schema), yet the description provides no explanation of any parameter. The agent must infer meaning solely from parameter names and schema types, which is insufficient for correct invocation, especially for optional parameters like 'display_date' and '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 it retrieves subdomain traffic distribution for a domain, distinguishing it from other traffic tools (e.g., semrush_traffic_sources) by focusing on subdomains. However, it does not specify the exact output format or differentiate from very similar tools like semrush_subdomain_* siblings.

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 lacks guidance on when to use this tool versus alternatives. It does not mention use cases, prerequisites beyond the '.Trends' requirement, or scenarios where a different tool might be better. No exclusions or contextual hints are provided.

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