yeastar_get_extension_group

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

With no annotations, the description must signal behavioral traits itself. 'Get' implies a read operation and 'Requires an ID' implies validation dependency on an existing list result, but the description does not disclose error behavior, output format, or permission requirements.

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, compact sentence conveys the purpose and prerequisite without filler. The most important scoping information appears first.

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 one-parameter read tool with no output schema, the description gives an agent everything needed to select and invoke it. Minor omissions like expected response shape or invalid-ID behavior are acceptable at this low complexity level.

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 coverage is 100% and the only parameter id is already documented as 'Object ID, from the corresponding list tool.' The description adds little beyond that, but it reinforces the correct provenance of the ID from yeastar_list_extension_groups.

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 opening verb 'Get' plus the object 'full detail (member extensions) for a single extension group' identifies both the action and resource. It is clearly distinguishable from sibling tools such as yeastar_list_extension_groups (all groups) and yeastar_get_extension (one extension) by specifying group scope and member-extensions detail.

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 states the required prerequisite: an ID from yeastar_list_extension_groups. It also clarifies that this is for a single group, so an agent knows to first list groups when no ID is available, though it does not explicitly enumerate when to prefer sibling alternatives.

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