semrush_url_organic

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

The description aligns with annotations (readOnlyHint=true, destructiveHint=false, idempotentHint=true) by stating 'Get', indicating a read operation. However, it adds no additional behavioral details such as data source freshness, rate limits, or result ordering. Given that annotations already cover the safety profile, the description is neutral but does not enhance transparency.

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, free of redundancy. It is concise and front-loaded. However, it could be slightly expanded to include key parameter context without losing brevity.

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?

The description is too sparse for the tool's complexity (3 params, no output schema, many siblings). It omits expected details such as return value structure, default limit, accepted database values, and any limitations. This leaves significant gaps for an agent.

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?

With 0% schema description coverage, the description bears full responsibility for explaining parameters, but it only mentions 'URL' implicitly. It fails to clarify meaning of 'database' (e.g., country code), 'limit' (e.g., max results), or constraints like minLength. This leaves the agent to infer or rely on external knowledge.

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 clearly identifies the resource ('organic keywords for a specific URL'). It effectively distinguishes this tool from siblings like semrush_domain_organic_keywords (domain-level) and semrush_url_adwords (paid keywords), making its purpose unambiguous.

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 explicit guidance on when to use this tool versus alternatives is provided. While the purpose is clear, there is no mention of when not to use it (e.g., for domain-level queries) or which sibling to prefer. The usage is implied by the name and description, but explicit context is missing.

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