pin_chat_message

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

There are no annotations, so the description must disclose behavioral traits itself. It does not mention side effects, such as whether a notification is sent, whether a previously pinned message is replaced, or any permission requirements. This lack of transparency leaves the tool's behavior largely unexplained.

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 concise at one sentence, but it is under-specified rather than efficiently informative. It omits crucial details about parameters and behavior, which reduces its value. Conciseness alone does not compensate for missing content.

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?

Despite the tool having 3 parameters and no output schema or annotations, the description only states the core action. It fails to provide necessary context about parameter usage, expected behavior, or any limitations, leaving the description incomplete for an AI agent to invoke correctly.

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%, and the description does not explain the purpose or semantics of any parameters (chat_id, message_id, disable_notification). The description adds no meaning beyond the parameter names themselves, which is insufficient given the lack of schema descriptions.

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 'Pin a message in a chat' clearly states the action (pin) and the resource (a message in a chat), distinguishing it from sibling tools like unpin_chat_message and delete_message. It is specific and unambiguous.

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 no guidance on when to use this tool versus alternatives such as unpin_chat_message, nor does it mention any prerequisites or conditions for pinning a message. There is no context about appropriate use cases.

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