get_group_contacts

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

With no annotations, the description must fully disclose behavior. It implies a read-only operation via 'List', but does not explicitly state non-destructiveness, error handling (e.g., invalid group_id), pagination, or response structure beyond what the output schema provides.

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 front-loaded sentence with no fluff. It efficiently conveys the core action, though it could benefit from breaking out usage notes or parameter details without adding excessive length.

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 presence of an output schema, the description does not need to detail return values. However, it lacks context on potential edge cases (e.g., empty group, missing group_id) and does not reference related tools like 'get_group_list', reducing completeness for a simple tool.

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 mentions 'by group_id' but adds no additional meaning beyond the parameter name. Since the schema has 0% description coverage, the description should explain what group_id represents (e.g., 'the ID from get_group_list') and any constraints, which it fails to do.

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 verb 'List' and the resource 'contacts in a given group by group_id', distinguishing it from siblings like 'get_contact_list' (all contacts) and 'get_group_details' (group metadata). The specificity of filtering by group_id makes the purpose 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 given on when to use this tool versus alternatives (e.g., using 'get_contact_list' for all contacts). There is also no mention of prerequisites, such as the group needing to exist or how to obtain a group_id.

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