bot_invite_link

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description is consistent with that by framing the tool as producing a link rather than mutating state. It adds genuine context beyond the annotations by disclosing that the generated permissions default to Administrator, a high-impact default an agent would otherwise miss.

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?

One sentence, front-loaded with the core output ('the link') and the default behavior in parentheses. It is efficient, though the noun-phrase framing rather than an action verb makes the opening slightly less scannable.

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?

For a two-optional-parameter, read-only tool with no output schema, the definition covers the essential facts: what it yields, who can use it, and the default permission level. Minor gaps remain around link expiry and required caller permissions, but the description is largely sufficient.

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 50%: the 'bot' parameter is documented in the schema ('Bot name or id; default bot if empty'), but the 'permissions' array is bare. The description partially compensates by stating the default is Administrator, yet it never explains what form the permission strings take or whether they are names, ids, or bitfields.

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 names the concrete resource it produces (an invite link) and the effect it enables (adding a bot to a server), which is more specific than a tautology. It does not, however, distinguish itself from the sibling 'add_bot' or 'create_invite', so an agent must infer whether this generates a URL or performs the addition.

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?

Usage is only implied: 'a server the user manages' signals a prerequisite (the caller must administer the target server), but there is no explicit when-to-use vs. when-to-call add_bot or create_invite. No exclusions or alternative routing is offered.

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