telegram-search-messages

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

Annotations already provide readOnlyHint=true and openWorldHint=true, so the description adds no new behavioral traits. It correctly implies a read-only search but does not elaborate on pagination, result ordering, or rate limits.

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 that front-loads the core action. It is efficient with no extraneous words, though it could benefit from a brief mention of optional parameters or result behavior.

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?

Given 5 parameters and no output schema, the description is minimal. It explains the basic purpose but omits details like result format, ordering, or pagination. The schema covers parameters adequately, but the tool's completeness could be improved with a note on return structure.

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 100% for 5 parameters. The description adds no additional meaning beyond 'by text', which is already captured by the query parameter. The date range and limit are not described in the description, but the schema already covers them.

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 action 'Search messages', the resource 'in a specific Telegram chat', and the filter 'by text'. This is unique among sibling tools like telegram-search-global and telegram-search-chats, making the tool's purpose distinct and unambiguous.

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 implies usage for text search within a specific chat but does not explicitly contrast with alternatives like telegram-search-global (global search) or telegram-search-sticker-sets. No when-not-to or prerequisites are mentioned.

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