get_groups_api_v1_groups

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

No annotations exist, and the description gives zero behavioral details, such as whether the operation is read-only, requires permissions, or returns a list. The output schema exists but is not mentioned.

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 extremely brief (two words) and lacks structure. While concise, it omits essential information, making it under-specified rather than efficiently concise.

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 complexity (sibling tools, optional parameter, output schema), the description is wholly inadequate. It does not explain what groups are, how to use the 'share' parameter, or how results are structured.

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 only parameter 'share' has no description in the schema or the tool description. With 0% schema description coverage, the agent cannot interpret its purpose (e.g., filter groups by sharing status).

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 'Get Groups' is a verb+noun but lacks specificity. It does not clarify whether it lists all groups or retrieves a group, and fails to distinguish it from sibling tools like 'get_group_by_id' or 'get_user_groups'.

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, such as get_group_by_id or get_user_groups. The agent has no criteria to decide.

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