discord_pin_message

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

No annotations are provided, so the description must disclose behavioral traits. It only states 'Pin a message', implying mutation but omits permissions, destructive nature (if any), rate limits, or side effects. Falls short of minimal transparency.

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?

Extremely brief (three words), but under-specifies the tool. Conciseness should not sacrifice necessary information; this is more omission than conciseness. Front-loading is irrelevant when content is missing.

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?

With no output schema, no annotations, and 0% parameter coverage, the description must compensate. It fails to convey required permissions, return values, or edge cases (e.g., already-pinned messages). Incomplete for an AI to use reliably.

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 description coverage is 0%; neither the schema nor the description explains what channelId and messageId represent. The description adds no meaning beyond the parameter names. Fails to clarify required identifiers or formats.

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 is a simple verb+resource ('Pin a message'), which is clear but does not differentiate from sibling tools like discord_unpin_message or discord_get_pinned. It lacks specificity about context (e.g., channel, scope).

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 (e.g., unpin, get pinned). No mention of prerequisites or conditions. The agent is left to infer usage from context.

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