Create Invite

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

Description explains all parameters and return value, including behavior of temporary and unique. Annotations indicate no destructive or idempotent effects, which matches. Could mention rate limits or permission checks, but current detail is good.

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?

Concise and well-structured: one-line summary, then Args list, then Returns. No fluff, every sentence adds information.

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?

Covers all parameters and return value. Lacks error cases, rate limits, or permission requirements. Given no output schema, the return description is adequate. Slightly above average completeness.

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 has 100% description coverage, so baseline is 3. Description adds value by clarifying parameter behavior (e.g., 'Kick members when they disconnect' for temporary, 'reuse existing' for unique). Marginally above baseline.

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 action 'Create' and the resource 'invite link for a channel'. It is specific and distinguishes this tool from siblings like discord_delete_invite and discord_list_invites.

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 guidance on when to use this tool vs alternatives. Does not indicate prerequisites like permissions or when not to use it. Missing explicit when-to-use/not-use or sibling differentiation.

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