get_recent_messages

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

Discloses that messages include human-friendly names and IDs are for follow-up calls. However, with no annotations, it omits behavioral traits like data freshness, caching behavior, or any side effects (e.g., cache invalidation).

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?

Three concise, front-loaded sentences with no redundancy. Every sentence adds value: purpose, return field format, and usage warning.

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?

Adequate for a simple retrieval tool but lacks explicit return structure (only mentions 'chat' and 'from' fields) and does not specify pagination or empty cache behavior. Given many siblings, could hint at differentiation.

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 0% schema description coverage, the description explains three of four parameters (hours, chatId, excludeGroups) in context but misses 'limit'. The explanations add meaning but are incomplete.

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 retrieves messages from the last N hours from local cache with optional filtering. The verb 'get' and resource 'messages' are specific, though it doesn't explicitly distinguish from sibling tools like 'search_messages' or 'get_brief'.

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 implicit guidance on when to use (for recent messages) and how to handle IDs, but lacks explicit when-to-use vs alternatives (e.g., 'search_messages' for richer queries) and no exclusions or prerequisites.

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