resolve_group_name

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

The description mentions reliance on an in-memory cache and case-insensitive substring matching, which are important behaviors. However, it does not disclose what happens if no match is found, if the cache is empty, or any potential side effects. Given no annotations, the description should offer more transparency.

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 consists of two concise sentences, front-loading the primary purpose in the first sentence and adding necessary context in the second. Every word serves a purpose with no redundancy.

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?

The tool is simple and has an output schema, reducing the need for return value explanation. However, the description omits crucial details about the 'fetch' parameter and behavior on multiple matches or no match, leaving gaps for an agent to understand its full usage.

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 explains the group_name parameter implicitly by describing the name resolution logic (case-insensitive, substring). However, the 'fetch' boolean parameter is entirely unexplained, leaving ambiguity about its purpose. With 0% schema coverage, the description fails to compensate adequately.

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 resolves a group name to known IDs, specifying case-insensitive substring matching and session cache usage. This distinguishes it from sibling tools like get_group_list or get_group_details, which serve different purposes.

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 implies usage after prior tool calls to populate the cache (e.g., get_group_list), but it does not explicitly state when to use this tool versus alternatives, such as direct group ID lookups, nor does it provide conditions for not using it.

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