Solafon MCP

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

With no annotations provided, the description carries full burden but only states the action without disclosing behavioral traits like permissions needed, rate limits, or what information is returned. It's a basic read operation, but lacks details on safety, response format, or constraints beyond the conversation 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?

The description is a single, clear sentence that efficiently states the purpose without waste. It's front-loaded and appropriately sized for a simple tool, though it could be slightly more structured with added context.

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 no annotations, no output schema, and a simple input schema, the description is incomplete. It doesn't explain what user information is retrieved, response format, or any behavioral aspects, leaving gaps for the agent to infer usage in a conversational context.

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%, so the schema fully documents the single 'userId' parameter. The description adds no additional meaning beyond implying the user must be in a conversation, which doesn't enhance parameter understanding. Baseline 3 is appropriate as the schema handles the heavy lifting.

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 verb ('Get') and resource ('information about a user'), specifying the user must have a conversation with the bot. However, it doesn't distinguish this from potential sibling tools like 'get_bot_info' or 'list_conversations' in terms of scope or relationship, keeping it from a perfect score.

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 minimal guidance by implying usage for users in conversation with the bot, but it lacks explicit when-to-use rules, prerequisites, or alternatives. No comparison to siblings like 'list_conversations' or 'get_bot_info' is made, leaving the agent with vague context.

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