export_invite_link

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

The description explains parameter effects (e.g., expiration, usage limit, approval requirement) but does not disclose broader behavior like side effects, permissions needed, or error conditions. Since annotations are absent, the description carries full burden and provides adequate but not comprehensive 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 is concise, using a clear list format without redundant information. Every sentence contributes value, and the structure is easy to parse.

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 description covers the tool's parameters well, and since an output schema exists, return values are not required. However, it omits context like required permissions or whether the tool is read-only or destructive, which would be beneficial given the lack of 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 description adds meaning beyond the input schema by explaining each parameter's purpose and providing example values (e.g., `+7d` for expires_at). With 0% schema coverage, this compensation is effective, though additional detail on valid ranges or constraints would improve it.

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's function: generating an invitation link for a group or channel. It uses a specific verb-resource combination and distinguishes itself from sibling tools by its unique purpose.

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 lacks guidance on when to use this tool versus alternatives. There is no mention of prerequisites (e.g., being an admin), scenarios where it should not be used, or comparisons to other tools.

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