Получение списка VCS провайдеров

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

The description claims a read-only operation ('gets list') while the annotation readOnlyHint=false indicates the tool may not be read-only. This is a direct contradiction between the description and the annotation, so the description fails to provide consistent behavioral context.

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, short sentence that directly states the function. Every word is necessary, and it is appropriately concise for a zero-parameter list tool.

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 simple list tool with no parameters and no output schema, the description provides the essential purpose. It includes 'all added' which clarifies scope. However, it lacks any detail about return format or behavior beyond listing, but the simplicity of the tool makes this acceptable.

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 has zero parameters, so the baseline is 4. The description doesn't need to explain parameter semantics as there are none, and the empty input schema is fully covered.

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 uses a specific verb 'получает' (gets) and resource 'список всех добавленных VCS провайдеров' (list of all added VCS providers), clearly distinguishing from sibling tools like add_vcs_provider and get_vcs_provider_repositories. It is unambiguous.

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 implies usage by stating it retrieves a list, but it does not explicitly state when to choose this over similar tools, nor does it mention any alternatives or exclusions. No when-to-use context beyond the obvious.

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