semrush_subdomain_rank

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

Annotations already provide readOnlyHint, destructiveHint, and idempotentHint, which cover the safety profile. The description adds no extra behavioral context (e.g., rate limits, authentication, output behavior) beyond what the annotations imply, so it does not significantly add value.

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 short sentence, making it concise but lacking structure. It could be expanded to include key details like parameter usage or output format without becoming verbose, so it earns a middling score.

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 (3 parameters, no output schema, many sibling tools), the description is too minimal. It does not explain what 'ranking data' means, the output structure, or how to effectively use parameters like database and limit. The agent lacks sufficient context to use the tool correctly.

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%, and the description does not explain the meaning or expected values for parameters (subdomain, database, limit). For example, 'database' has a default but no list of valid databases, and 'limit' lacks context on what it limits (e.g., results count). The description fails to compensate for the missing schema descriptions.

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 ranking data for a subdomain in a specific database', which is a clear verb+resource. However, it does not differentiate from similar sibling tools like semrush_subdomain_organic or semrush_subdomain_ranks, so the purpose is clear but not distinct enough for an agent to choose correctly among alternatives.

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 siblings. The description does not mention any exclusions, prerequisites, or scenarios, leaving the agent without context for selection.

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