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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered structurally. The description usefully adds that the tool opens nothing by itself and returns instructional content, which confirms the read-only nature. However, it does not say whether a Cloud Browser session must already exist, whether calling it has any side effect on the account, or how the step-by-step output is shaped beyond 'screens, buttons, fields'.

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 operational content is front-loaded and tight, but roughly half the text is a tangent about Discord's official API and the absence of an official MCP server, including a check date. That context may justify the browser approach but does not help an agent invoke this specific tool, so it dilutes an otherwise two-sentence definition.

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 zero-parameter, read-only guide tool with no output schema, the description covers what it returns, that it performs no action itself, and which tools complete the task. It is nearly sufficient on its own. It stops short of stating any precondition about the Cloud Browser session or account context, which is the one remaining operational unknown.

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 input schema has zero parameters and 100% coverage, so there is nothing for the description to disambiguate. Baseline for a no-parameter tool is 4. The description does not need to explain inputs and correctly does not try.

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 a specific resource and action (pinning a message in the user's Discord account) and immediately qualifies that the tool returns step-by-step instructions rather than performing the pin. It distinguishes itself from the cotlet_browser_* siblings by saying it 'opens nothing by itself' and that the actual action happens elsewhere. The only weakness is that the leading verb 'Pin message' momentarily reads as a direct action before the clarification.

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?

It gives explicit sequencing: call this to get the screens/buttons/fields, then execute with the cotlet_browser_* tools in the user's Discord Cloud Browser. That is clear when-to-use guidance plus the follow-up path. It does not address when to prefer this browser path over bot-based siblings like discord_send_message, leaving one routing question unanswered.

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