discord_list_pinned_messages

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

Annotations are absent, so the description carries the full burden for behaviors. It correctly predcribes listing rather than mutating and Stesor implies a read-only action. But it does not disclose permission requirements or read-only status explicitly; nonetheless the stated behavior is accurate.

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?

A single sentence that is front-loaded with the primary operation and scope. There is no redundant wording or filler.

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 straightforward listing operation, the tool name and description plus output schema may be enough to call the main channel. The lack of clarity about the optional guild_id and the total absence of usage boundaries keep it from being fully complete.

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 description explains only the channel context, which maps to channel_id. It says nothing about the optional guild_id parameter, and the schema offers no property descriptions, so the purpose of that parameter remains unexplained. Since schema description coverage is 0%, the description needed to compensate and did not.

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 uses a specific verb (list), a specific resource (pinned messages), and a clear scope (in a channel). It is easily differentiated from sibling tools like discord_get_recent_messages or discord_pin_message.

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 implies when to use the tool: whenever the agent needs pin_part messages from a channel. There is no explicit statement about when not to use it or which alternative to prefer, but the wording provides enough implied context.

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