semrush_subdomain_ranks

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, providing safety profile. The description adds no additional behavioral context beyond what annotations provide. It does not disclose return format, pagination, or what 'ranking data' entails.

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 extraneous information, achieving maximum conciseness for its length.

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?

For a tool with 2 parameters, no output schema, and many siblings, the description is too brief. It does not indicate that the tool returns a list of ranks per database, nor does it clarify the format or expected output, leaving the agent with incomplete 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 should compensate. It mentions 'subdomain' but does not explain its format or provide examples, and the 'limit' parameter is completely ignored. The parameter names are somewhat self-explanatory but insufficient for precise usage.

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 'ranking data for a subdomain' and notes 'across all databases', indicating it returns multiple rankings. However, it does not distinguish itself clearly from similar sibling tools like 'semrush_subdomain_rank' which likely returns a single rank.

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 on when to use this tool versus alternatives such as 'semrush_subdomain_rank' or 'semrush_domain_organic_keywords'. The agent must infer from the name and description, which is insufficient for proper selection among many similar sibling tools.

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