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 useful content-level context beyond that: the payload is a fixed set of 10 competencies with descriptions and links to thematic collections, which tells the agent this is a closed, static catalog with no side effects.

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 front-loaded sentence that labels the resource first and then enumerates its contents. No filler, though the 'Справочник:' prefix is slightly redundant with the title.

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 parameters, no output schema, and simple read-only annotations, the description supplies exactly what is needed: what the catalog contains (10 competencies, descriptions, collection links) and that it is a static reference. Nothing required to invoke it correctly is missing.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the schema is trivially complete. Baseline of 4 applies for a no-argument tool.

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 resource and scope: a reference of exactly 10 managerial competencies in the RuForge model, each with description and links to thematic collections. An agent can tell this is a static reference lookup rather than a diagnostic or profile tool. It stops short of naming the nearest sibling (ruforge_get_maturity_levels), which is why 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?

The word 'Справочник' implies a lookup use case, but there is no explicit when-to-use statement, no prerequisites, and no mention of alternatives such as ruforge_get_maturity_levels or ruforge_kb_search, which also return catalog-style content. The agent must infer routing on its own.

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