discord_add_friend

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

No annotations are provided, so the description carries full responsibility. It merely states 'Send a friend request' without disclosing whether this adds a direct friend or sends a pending request, rate limits, permission requirements, or side effects like rate limiting.

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 a single, well-structured sentence that immediately conveys the core purpose. It is concise, but could be slightly expanded to include usage constraints without losing efficiency.

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 three optional parameters, no output schema, and a vast set of sibling tools, the description is too brief. It omits what the tool returns (e.g., a friend request object or success confirmation), error scenarios, and the nature of the friend request (pending vs. immediate acceptance).

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 0%, so the description must explain parameter usage. It does so by noting two identification methods (userId or username+discriminator), but it fails to define 'discriminator' (e.g., the four-digit tag) or clarify that exactly one method should be used. The guidance is partial.

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 ('Send a friend request') and specifies the identification methods (by userId or username+discriminator). It distinguishes this tool from its many siblings, which cover guild, message, role, and other operations.

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 provides no guidance on when to use this tool versus alternatives like discord_get_user or discord_ban_user. There is no mention of prerequisites, such as the need for a mutual relationship or existing user interaction.

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