search_messages

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

Fails to explain why a search operation is marked destructive=true in annotations, or what openWorldHint implies for search scope.

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?

Extremely terse at 6 words; while front-loaded, it lacks necessary detail given the destructive hint and complex sibling relationships.

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?

Missing critical context: no explanation of return value structure (no output schema), pagination behavior, or the counter-intuitive destructive classification.

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?

With 100% schema description coverage, the description meets baseline expectations but adds no additional parameter context (e.g., query syntax, limit constraints).

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?

Clearly states the tool searches messages by keyword in a Telegram chat, distinguishing it from sibling 'get' tools that retrieve messages by date or pinned status.

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?

Provides no guidance on when to use search vs. get_messages or get_messages_by_date, nor any exclusion criteria.

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