groupChat_getInviteCode

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

No annotations are provided, so the description carries full responsibility for disclosing behavior. It only says 'Get the invite code' without mentioning permissions, return format, failure modes, or that it is a read-only operation. Minimal additional transparency beyond the name and schema.

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 redundant: 'Get the invite code' is repeated with minor addition 'for a specific group'. This wastes a sentence and could be condensed to one clear phrase. The structure is also awkward with the '[Group Chat]' prefix.

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 no output schema, the description should explain what the tool returns (e.g., the invite code string) and any caveats. It doesn't. For a simple getter it may be sufficient, but it lacks clarity on results, prerequisites, or error handling, making it incomplete for an agent to fully anticipate behavior.

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 coverage is 100% with both parameters well-described (chatId as 'Unique WhatsApp id for the given chat group' and sessionId as 'Unique identifier for the session'). The description adds no parameter-specific details, so the baseline of 3 applies.

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 the verb 'Get' and resource 'invite code', and clarifies 'for a specific group', which distinguishes it from tools like groupChat_revokeInvite or client_getInviteInfo. However, it is redundant, repeating 'Get the invite code' twice, and doesn't explicitly name alternatives.

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 gives no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., being a group admin), when not to use it, or that it should be used to share an invite code. Siblings like groupChat_revokeInvite differ, but no differentiation is provided.

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