discord_pin_message

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

The description adds value beyond annotations by detailing the permission requirement, channel pin limit, and idempotent behavior. Annotations already indicate idempotentHint=true and destructiveHint=false, so the description enriches context without contradiction.

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?

Three concise sentences front-load the core purpose and then add essential context (permission, limits, idempotency). Every sentence earns its place with no wasted words.

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 a simple input schema and no output schema, the description covers all relevant aspects: purpose, permission, limits, and behavioral guarantees. It lacks explicit mention of response/return behavior, but that is not critical for a basic mutation tool.

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?

All parameters are fully described in the schema (100% coverage). The description reinforces the 'pin' parameter role but does not add new meaning beyond what the schema already provides. Baseline score of 3 is appropriate.

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 states the exact action ('Pin or unpin a message in a channel') and the control flag, making the tool's purpose immediately clear. It distinguishes itself from sibling tools like discord_delete_message or discord_add_reaction by focusing solely on pinning/unpinning.

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 explicit usage guidelines: it requires the 'Pin Messages permission' and notes the 50-pin channel limit and idempotency. While it does not explicitly compare to sibling tools, the narrow purpose and constraints sufficiently guide when to use this tool.

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