semrush_income_distribution

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the safety profile is covered. The description adds only the '.Trends' requirement, which is a prerequisite, not a behavioral trait. It fails to disclose response format, data limits, or any other behavioral details beyond what annotations 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 extremely concise (one sentence), which is positive, but it sacrifices necessary detail. It front-loads the main action but omits parameter guidance and context. It is appropriately sized for a simple tool but incomplete for a 5-parameter tool.

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 complexity (5 parameters, no output schema, 0% schema coverage), the description is severely incomplete. It does not describe what 'audience' refers to, how the output is structured, or any edge cases. With no output schema, this lack of description leaves agents without essential context for choosing and using 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%, yet the description provides no explanation of any parameters (target, country, device_type, display_date, limit). It does not clarify what 'target' represents or how the optional parameters affect results. The description adds no semantic value beyond the raw schema.

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 a clear verb and resource: 'Get income distribution of audience'. It also mentions a prerequisite ('.Trends'). However, it does not differentiate itself from sibling tools like semrush_education_distribution, semrush_household_distribution, or semrush_occupation_distribution, which share similar purpose patterns.

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 includes a usage condition: 'requires .Trends'. But it provides no explicit guidance on when to use this tool versus alternatives, nor does it specify any context exclusions. The usage is implied but not fully explicit.

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