get_logged_in_user_group

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

With no annotations, the description carries the full burden. It does indicate the operation is a read via the GET endpoint and the 'read-only' keyword, but it says nothing about authentication requirements, scope of returned group data, or error behavior for unauthenticated callers.

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 definition is dominated by a redundant keyword block ('get group self, fetch group self, read group self...') that repeats the same phrase a dozen ways. The genuinely informative content is two short lines buried at the top and bottom.

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 zero-parameter read tool with no output schema, the description conveys who the data is for (the current user) and where it comes from, which is minimally sufficient. It omits what fields the group data contains and any auth prerequisite, leaving gaps for a tool with no annotations.

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 tool takes zero parameters, so per the rubric the baseline is 4. The description correctly implies no inputs are needed by describing the call as fetching the current user's own group.

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 clear verb+resource ('Get group self', 'Returns the Group Data for the Current User') and pins the exact endpoint [GET /api/groups/self], which separates it from siblings like get_group_members or get_group_preferences. The keyword dump dilutes it, but the core purpose is 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 when-to-use guidance is given and no alternative sibling is named. An agent cannot tell from this text whether to prefer this over get_logged_in_user_household or get_group_member for a given need.

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