keyso_post_tools_check_top_concurents_urls

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

No annotations are provided, so the description carries the full burden, but it only states method, path, and an example URL. It does not disclose what the POST does, whether it is asynchronous, what it returns, whether it mutates state, or any auth/rate-limit implications. This is essentially endpoint metadata, not behavioral disclosure.

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 text is compact and front-loads the semantic phrase before the transport details, with no fluff. However, the main semantic phrase is a fragment ('Подсветка топов - страницы конкурентов') and the description is so terse that it sacrifices meaningful content for 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?

For a POST endpoint with a nested body parameter, no output schema, no annotations, and many closely related sibling tools, this description is incomplete. An agent can infer how to form a basic request URL from the example, but cannot determine expected body contents, response format, or when to pick this over check_top_concurents_domains.

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 coverage is 100%, so each parameter at least has a description, though most are minimal ('in: query', 'JSON body', 'API token override'). The description adds the useful example base=msk, hinting at the base parameter's meaning. However, the body object is left entirely opaque with no properties or structure explained.

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 endpoint path and name clearly identify the resource as competitor URLs ('check-top-concurents-urls', 'страницы конкурентов'), and the example request shows the base parameter in action. However, it does not explicitly differentiate itself from sibling tools like check_top_concurents_domains, so the distinction is mostly inferred from the name.

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 provides only a request example and no guidance on when to use this tool versus alternatives such as keyso_post_tools_check_top_concurents_domains or keyso_post_tools_check_top. There are no scenarios, exclusions, or conditions stated.

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