pin_message

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

Annotations are absent, so the description carries the full burden. It does disclose a meaningful behavior: notify=false suppresses notifications to participants. However, it does not mention other relevant effects, such as whether pinning overwrites an existing pinned message or requires special permissions.

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 a single front-loaded sentence stating the action, immediately followed by the key parameter caveat. No filler or redundancy; every word earns its place.

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?

An output schema exists, so return values need not be described. The description covers the main behavioral flag but omits important context like prerequisites (e.g., permissions), whether the pin replaces an existing one, and when to use this tool versus unpin_message. Adequate for a simple mutation, but gaps remain.

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%, so the description must compensate. It explains the notify parameter explicitly. The chat and message_id parameters remain undocumented in the description, though their names are fairly self-evident in context. Partial compensation.

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 clear verb and resource: 'Закрепить сообщение' (pin message), which is specific and easily distinguished from siblings like unpin_message by opposite action. However, it does not explicitly name or differentiate itself from that sibling within the text.

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 is provided on when to use this tool versus alternatives such as send_message or unpin_message. The only usage-related hint is about the notify parameter, which is a parameter behavior note rather than tool-selection guidance.

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