bale_pin_message

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

No annotations are provided, so the description carries the full behavioral burden for a mutation tool. It does not say whether pinning requires elevated permissions, whether it replaces an existing pin, or what happens if the message is already pinned; 'private chat or group' is the only behavioral nuance offered.

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 short sentence with no wasted words, so structure is fine, but its brevity reflects under-specification rather than efficiency. There is no front-loaded detail to build on.

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, but with 0% param coverage, no annotations, and a mutating operation, the definition is too thin. An agent would need to guess the meaning of just_me and the permission requirements.

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% across 4 parameters, so the description must compensate and largely does not. Its phrase 'private chat or group' loosely gestures at chat_type, but chat_id, message_id, and especially the just_me flag are left completely unexplained.

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?

States a specific verb and resource ('Pin a message') plus a scope qualifier ('in a private chat or group'), so the agent knows the operation. It does not differentiate from any sibling, though no unpin sibling exists, so the ambiguity risk is low.

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?

There is no guidance on when to use this tool, no prerequisites (e.g., admin rights in a group), and no mention of alternatives such as sending or editing a message. The agent must infer the context entirely.

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