get_pinned

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

The description explicitly states 'read-only', which is a useful safety trait given no annotations are provided. However, it does not disclose authorization requirements, rate limits, pagination, or error behavior, and the 'T12/iter_messages' reference adds little behavioral clarity.

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 very concise and front-loaded with the core purpose. However, the 'T12: get_pinned / iter_messages(pinned)' segment is cryptic and arguably unnecessary for an agent, reducing clarity slightly.

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?

This is a simple one-parameter read-only tool with an output schema, so return values need not be described. Still, the absence of any usage guidance or parameter format details leaves some gaps, though the core purpose is clear.

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 only parameter 'chat' is a required string with schema description coverage of 0%. The description mentions 'чата' (of chat), but this merely restates the parameter name and does not specify format (ID vs username), validation rules, or how it should be obtained.

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 retrieves pinned messages of a chat, a specific resource that distinguishes it from siblings like get_history or list_chats. The verb 'get' is implied by the name and reinforced by the phrase 'pinned messages of chat'.

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 get_history or search_in_chat. The 'T12: get_pinned / iter_messages(pinned)' reference is an implementation hint, not usage guidance.

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