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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuine context beyond that: the returned fields (title, author/reviewer, date, body with section headings, tables, source links) and a usage obligation ('Цитируйте с указанием URL'). It does not mention truncation behaviour when max_chars is hit, which keeps it from a 5.

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?

Two sentences, front-loaded with the core purpose, then the provenance hints, then the citation rule. No filler or restatement of the tool name.

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?

With no output schema, the description usefully enumerates the return content so the agent knows it receives structured article text plus metadata. The only gap is not describing what happens when the article exceeds max_chars, which matters for long materials.

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% and slug already has an example in the schema, so the baseline is 3. The description earns above that by explaining where the slug value comes from (URL path segment or ruforge_kb_search output), which the schema does not say. max_chars is left entirely to the schema, which is acceptable given its full documentation.

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 states a specific verb+resource combination ('Полный текст материала базы знаний RuForge по slug') and immediately distinguishes itself from sibling tools by naming ruforge_kb_search as the source of the slug and the URL path pattern. An agent can tell that this tool retrieves a single article's full content, not a search or recommendation.

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?

Usage is clearly implied: the slug originates from a /knowledge-base/<slug>/ URL or a prior ruforge_kb_search result, which routes the agent to search first. There is no explicit when-not-to-use statement or warning about overhead of fetching full text versus the search snippet, but the context is clear.

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