pin_dialog

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

The description adds the behavioral detail that the dialog is pinned to the top of the list ('в шапке списка'), which is useful. However, it does not disclose potential side effects (e.g., max pins, overriding existing pins) or permission needs. Annotations already cover readOnly=false and destructive=false, but the description adds limited value beyond that.

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, concise sentence with no unnecessary words. It is appropriately sized and front-loaded with the core action.

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?

The tool has a simple purpose and an output schema exists, but the description is too minimal. It lacks parameter semantics and usage guidance, leaving the agent without enough information to reliably invoke the tool. The description covers only the basic action, ignoring important details like parameter meaning and expected behavior for different inputs.

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 parameters 'chat' or 'pinned'. The description implies the action of pinning/unpinning but does not clarify what types of values 'chat' accepts (integer or string) or how 'pinned' controls the action. This is a significant gap.

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 clearly states the tool's function: to pin/unpin a dialog at the top of the list. The verbs 'pin/unpin' are specific and the resource 'dialog' is identified, distinguishing it from sibling tools like pin_message or pin_forum_topic.

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, nor does it mention any prerequisites or conditions (e.g., permission requirements). It simply states the action without context.

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