create_invite_link

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 says 'Generate an invite link' but does not disclose whether this creates a new link each call, whether previous links remain valid, what permissions are needed, or what side effects occur. For a tool that produces a shareable resource, this is insufficient.

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: a one-sentence summary followed by parameter explanations in a structured format. Every word serves a purpose, and information is front-loaded. No redundancy.

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 tool's simplicity (2 parameters, no output schema, no nested objects) and lack of annotations, the description adequately explains parameters. However, it omits crucial details like the return value (what kind of link?), error conditions (invalid category, expired duration), and whether the link can be managed later. This leaves gaps for an AI agent.

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 schema has no descriptions (0% coverage), so the description adds essential meaning: 'shared_category_id' is linked to categories with non-null mode from 'list_categories', and 'duration_hours' is described as 'Link validity in hours'. This clarifies purpose beyond the schema's type and default.

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 'Generate an invite link to share with others', which is a specific verb+resource. It distinguishes from siblings like 'create_shared_category' (creates the category) and 'add_to_shared_category' (adds users directly). However, it could be more precise about the context (e.g., for a shared category).

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 guidance for the 'shared_category_id' parameter: 'Shared category ID (from list_categories — pick ones where mode is not null)', which helps select the right category. However, it does not explicitly state when to use this tool vs alternatives like 'agent_magic_link' or 'add_to_shared_category', nor does it mention prerequisites or limitations.

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