terminal_groups__get_terminal_groups

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

Annotations already establish readOnlyHint=true and destructiveHint=false. The description adds useful behavior beyond that: MCP-server throttling of 10 requests per 60 seconds and a caching recommendation. It also states the result is a list of terminal groups.

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 short, front-loaded with the purpose, and organized into Args/Returns/ID-source/throttling sections. The 'request: Параметры запроса TerminalGroupsRequest' line is somewhat redundant with the schema, but the overall size is appropriate.

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 list tool with no output schema, the description covers purpose, parameter sourcing, and rate limiting. It is missing response structure details and does not address the closely related sibling tools, leaving some ambiguity for an agent deciding between them.

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 description names the request object and points the agent to organizations__get_organizations for organizationIds, which adds cross-tool meaning. However, it does not explain includeDisabled or returnExternalData, and with a 0% schema coverage signal it only partially compensates for parameter 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 clear verb and resource: 'Получить терминальные группы' (get terminal groups). However, it does not distinguish this tool from the sibling terminal_groups__get_terminal_groups_by_organization or check_terminal_groups_availability, so it misses the differentiation required for 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 description gives no guidance on when to prefer this tool over its siblings. It does explain where to obtain organizationIds from organizations__get_organizations, but that is dependency guidance, not selection guidance.

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