semrush_subfolder_ranks

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

Annotations already declare readOnlyHint, destructiveHint, and idempotentHint, so the safety profile is clear. The description adds no extra behavioral context (e.g., pagination, limit behavior, response structure). It meets the minimal bar but does not leverage the opportunity to 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, which is concise but too terse. It sacrifices necessary parameter and behavioral information. While front-loaded with the core purpose, it lacks completeness.

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 low schema coverage (0%) and no output schema, the description should provide more context for correct invocation. It does not explain how to specify a subfolder (e.g., leading slash, relative path) or the effect of the limit parameter. Annotations cover safety but not usage nuance.

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 either parameter. 'subfolder' is not defined (format or type), and 'limit' is not mentioned. The description fails to compensate for the missing schema descriptions, leaving the agent without essential parameter semantics.

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?

Description clearly states the action ('Get ranking data'), the resource ('for a subfolder'), and scope ('across all databases'). It effectively differentiates from siblings like semrush_subfolder_rank (likely per-database) by implying global aggregation.

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 vs alternatives like semrush_subfolder_rank, semrush_subdomain_ranks, or semrush_url_ranks. The description does not mention prerequisites, context, or when not to use it.

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