list_group_members

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

Annotations already establish readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered by structured metadata. The description adds the set of valid group_type values but does not disclose behavior such as what happens for nonexistent groups or what data the returned member list contains. This is adequate but not rich.

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 contains no wasted content. The Args block concisely clarifies both parameters without verbose or redundant explanation. The bilingual note adds clarity without bloat.

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 read-only listing operation with only two required parameters, the description plus annotations provide enough information to invoke the tool. The absence of an output schema is mitigated by the clear 'List members' phrasing, though a note about the exact return format would make it fully complete.

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 carry the semantic load. It provides meaningful explanations for both parameters: group_type is defined with the allowed values 'structure', 'boundary', and 'load', and name is identified as the group name. This goes beyond the bare schema but could add more detail about name lookup or formatting.

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 specific action ('List members') applied to a clear resource (structure/boundary/load group) and enumerates the allowed group types. This clearly distinguishes the tool from sibling group-management tools like add_elements_to_group, remove_from_structure_group, and create_structure_group.

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 about when to use this tool instead of alternatives such as get_model_data, find_entities, or other group-related queries. The intended context is only implied by the name and description, with no when-to-use or when-not-to-use information.

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