keyso_post_tools_check_top_concurents_domains

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

With no annotations, the description must carry the behavioral disclosure burden. It only states Method and Path and gives an example URL; it does not mention authentication, side effects, response shape, or whether the call is synchronous/asynchronous.

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 short and front-loaded: purpose phrase, method, path, and example occupy only four lines with no filler. The structure is scannable, though the opening phrase is somewhat vague.

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 tool with no annotations and no output schema, the absence of response information and parameter semantics makes the description incomplete. An agent could issue the example request but cannot know what to expect in return or how to configure the body.

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 100%, so the baseline is 3. The description adds one useful example (base=msk) but no real semantic explanation for base, body, token, or base_url; the schema's own descriptions are mostly mechanical.

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 phrase 'Подсветка топов - сайты конкурентов' and the path '/tools/check-top-concurents-domains' indicate the tool deals with competitor domains in top results, but there is no explicit verb or statement of what the tool returns. It does not distinguish itself in prose from closely related siblings such as check_top_concurents_urls or check_top.

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 gives no when-to-use guidance, prerequisites, or alternatives. The only contextual hint is the example base=msk, which implies a regional parameter but does not explain how to choose this tool over the many competitor/report siblings.

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