b24_im_recent

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

Annotations already readOnlyHint, idempotentHint, destructiveHint false. Description adds return fields (DIALOG_ID, last message, unread counters). No contradiction. Additional behavioral details (e.g., pagination) not mentioned.

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?

Two sentences, no redundant words. Action verb first. Efficiently conveys purpose and post-use guidance.

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?

Has output schema; description mentions key fields. Lacks ordering or date-range hints but sufficient for a list tool.

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 coverage 100%, schema fully documents all 3 parameters with descriptions. Description adds no new parameter info beyond schema. Baseline 3 appropriate.

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?

Explicit verb and resource: 'List the acting user's recent chats/dialogs'. Names the API method (im.recent.get). Distinguishes from sibling b24_im_dialog_messages by mentioning use of DIALOG_ID for history.

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?

States clear next step: 'Use a DIALOG_ID with b24_im_dialog_messages to read history.' Provides context but no explicit when-not-to-use or alternatives among many IM siblings.

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