generate_invite

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

No annotations are provided, so the description carries the full burden. It mentions admin-only access and default 24-hour expiration, which are key behavioral traits. However, it does not disclose any side effects, rate limits, or return value behavior. For a simple generation tool, this is adequate but not comprehensive.

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 concise with only two sentences, no wasted words. It is front-loaded with the purpose and includes key constraints.

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 has two optional parameters and no output schema. The description does not specify the output format or how the invite code will be returned. It also does not explain the default role behavior. While the sibling list includes 'register_agent' for context, the description is incomplete for a full understanding.

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 compensate. The description does not explain the 'role' or 'expires_in_hours' parameters, leaving their meaning unclear. The default expiration is implied but not linked to the parameter. The agent may not understand how to customize the invite behavior.

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 generates a new Agent invite code. The verb 'generate' and resource 'invite code' are specific. The purpose is unambiguous and distinct from sibling tools like 'register_agent'.

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 explicitly states that only admins can call this tool, providing clear usage context. It does not mention when not to use or alternatives, but the admin restriction is a strong guideline.

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