discord_pin_message

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

With no annotations available, the description must carry the full behavioral transparency burden. It does disclose the 50-pin limit, which is useful, but it does not mention potential failure conditions (e.g., exceeding the limit, missing permissions) or any side effects beyond the pinning action itself.

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, tightly worded sentence. The primary action is front-loaded, and there is no superfluous information. It achieves high clarity with minimal length.

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 simple tool with no output schema, the description covers the essential behavior and mentions the key constraint. It lacks only a note about permissions or error scenarios, but these are not critical for basic understanding or invocation. Overall, it is sufficiently complete for this complexity level.

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 already provides clear descriptions for both channelId and messageId, and the tool description adds no further semantic detail about these parameters. Since schema coverage is 100%, the baseline score of 3 is appropriate; no extra value is contributed.

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 primary action ('Pins a message to its channel') with a specific verb and resource. It is immediately obvious what the tool does, and it is distinct from sibling actions like unpinning or listing pinned messages.

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 explicit guidance is provided about when to use this tool versus alternatives such as discord_unpin_message or discord_list_pinned_messages. The mention of the 50-pin limit is a constraint, not usage direction, so the description lacks the 'when to use vs alternatives' clarity.

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