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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds useful behavioral context by disclosing that results are aggregated from several relation types and grouped by type, which is beyond the annotations. It says nothing about result volume, ordering, or what happens when no relations exist.

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 compact sentence that front-loads the resource and then enumerates the relation types and the grouping behavior. No filler, though the comma-heavy enumeration is slightly dense.

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 read-only, two-parameter lookup with no output schema, the description adequately conveys what kinds of relations are returned and how they are grouped. It omits the undocumented limit parameter, result count bounds, and behavior on missing input, leaving the picture only partly complete.

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 50%: slug is documented ('slug или URL') but limit (default 8, max 20) has no description in either the schema or the description text. The description only implicitly ties the input to 'указанный' material and never explains the limit param or its bounds, so it fails to compensate for the coverage gap.

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 names a specific resource (related materials for a given item) and enumerates the relation kinds (direct outbound/inbound links, shared topics, roles, technologies) plus the output grouping. This clearly separates it from siblings like get_article or search_knowledge. It stops short of an explicit verb and does not name the sibling alternatives, so it is not a 5.

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?

There is no when-to-use or when-not-to-use guidance and no mention of alternatives, even though search_cases, search_knowledge, search_playbook and get_article all plausibly overlap. Usage is only inferable from the purpose sentence.

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