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

No annotations exist, so the description carries the full behavioral burden. It does disclose a meaningful output difference — with session_id each group gains a 'why' explanation of relevance to that user — but says nothing about whether the call is read-only, whether it requires a valid session, or what the recommendations contain.

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?

A single dense sentence with the primary purpose front-loaded and the conditional mode explained inline. The nested parenthetical is slightly heavy but no content is wasted.

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?

All three parameters are optional and no output schema exists, yet the description never says what happens if no arguments are given or whether the modes are mutually exclusive. The shape of the returned materials is only hinted at via the 'why' field, leaving real ambiguity for an agent deciding how to call it.

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 baseline is 3. The description goes beyond the schema by explaining the cross-parameter relationship: domain+level form one mode, while session_id selects a second mode that changes the response by adding a 'why' field per group.

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?

States a specific verb and resource ('рекомендации материалов для развития компетенции') and names both operating modes, domain+level and session_id. It is clearly distinguishable from the sibling ruforge_kb_search, which it references only for the slug format.

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?

Explicitly describes the two ways to invoke it: by competence level (domain + level) or from diagnostic results (session_id). It does not state exclusions or what happens when neither mode is supplied, and never names an alternative tool to use instead, but the context for each mode is clear.

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