Получить метки

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

No annotations are provided, so the description must disclose behavioral traits. It only states that labels are returned, without indicating whether the operation is read-only, if it has any side effects, or if authentication is required. The agent lacks information about potential dangers or restrictions.

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 description is a single concise sentence that directly states the tool's function. There is no unnecessary text, and it is front-loaded with the essential information. Every word earns its place.

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?

Given the tool's low complexity (one parameter, no nested objects), the description is adequate for basic understanding. However, it lacks information about the output format or structure, which would be helpful since no output schema is provided. The description is complete enough for a simple tool but leaves some ambiguity about the response.

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% for the single parameter 'id', but the description ('ID страницы') adds minimal value beyond the schema. It clarifies the parameter's purpose but does not elaborate on format, constraints, or examples. Baseline 3 is appropriate as the schema already conveys the necessary information.

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 clearly states that the tool returns labels of a page. It uses a specific verb 'возвращает' (returns) and resource 'метки страницы' (page labels), distinguishing it from sibling tools like confluence_add_labels and confluence_remove_label which have different purposes.

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 provides no guidance on when to use this tool versus alternatives. There is no mention of prerequisites, when not to use it, or which sibling tools to consider for related tasks. The agent must infer usage from the name and sibling list alone.

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