Get field group

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

The annotations declare readOnlyHint=true, so the safe-read nature is already known. The description adds no additional behavioral context—nothing about return format, error handling, permissions, or how entity_type affects behavior. It simply repeats the action implied by the title.

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, well-structured and front-loaded. However, it is nearly redundant with the title, adding only 'by ID', so it is concise but at the expense of substantive content.

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 tool with two required parameters, one of which (entity_type) is non-obvious, the description is incomplete. There is no explanation of how entity_type relates to field groups, what the response will include, or any caveats. The openWorldHint annotation is also unexplained, leaving the agent without sufficient context for correct invocation.

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 0%, so the description must compensate. It only mentions 'by ID', partially clarifying the id parameter, but gives no meaning for the required entity_type parameter with its enum of entity types. The description does not help an agent understand the purpose or valid values for entity_type.

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 the tool retrieves a specific field group by ID, distinguishing it from list, create, update, and delete siblings. The verb 'Get' and resource 'field group' are specific and 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?

No guidance is provided on when to use this tool versus alternatives like kommo_field_groups_list. It doesn't mention that this should be used when an ID is known, nor does it explain the need for entity_type. No usage context or exclusions are given.

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