Thenvoi MCP Server

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

With no annotations provided, the description carries the full burden. It effectively discloses key behavioral traits: it's a read operation (implied by 'Get'), specifies what data is included (agent messages and mentions), mentions chronological ordering, and describes pagination behavior. However, it doesn't cover potential errors, rate limits, or authentication needs, leaving some gaps.

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 appropriately sized and well-structured. It front-loads the purpose, then details what's included, usage context, message ordering, and parameters with clear sections. Every sentence adds value without redundancy, making it efficient and easy to parse.

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 the tool's moderate complexity (3 parameters, read operation), no annotations, and an output schema present, the description is complete enough. It covers purpose, usage, behavior, and parameters thoroughly. The output schema handles return values, so the description doesn't need to explain JSON structure, making this well-balanced.

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 schema description coverage is 0%, so the description must compensate fully. It successfully adds meaning beyond the schema by explaining all three parameters: 'chat_id' as the chat room identifier, 'page' for pagination with default, and 'page_size' with default and max value. This provides complete parameter semantics that the schema lacks.

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's purpose with specific verbs ('Get conversation context for agent rehydration') and resource ('agent chat context'). It distinguishes from siblings like 'get_agent_chat' (which likely returns chat metadata) by focusing on message retrieval for agent execution context, making the distinction explicit.

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 provides clear context on when to use this tool ('to load the complete context an external agent needs to resume execution'), but it doesn't explicitly state when not to use it or name specific alternatives among the sibling tools. The guidance is helpful but lacks explicit exclusions or comparisons.

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