Identify the logged-in username on Reddit, X, GitHub, or HN before commenting to avoid duplicate posts. Returns the username or 'unknown' when not detected.
Detect the currently logged-in username on the page (Reddit, X, GitHub, HN). Returns username or 'unknown'. Use before commenting to avoid duplicates.
| Name | Required | Description | Default |
|---|---|---|---|
| page_id | No | ||
| session_id | Yes |
Changes observed during successful MCP inspections.
v0.7.3Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden of behavioral disclosure. It explains that the tool returns 'username' or 'unknown', implying a read-only detection with a fallback value, and lists supported sites. It does not disclose detailed behavior around sessions, page state, or error handling, so some gaps remain.
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 two short sentences with no filler. The primary purpose is front-loaded, the return behavior is included, and the usage note earns its place.
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?
The tool lacks annotations, output schema, and parameter explanations. While the description covers purpose and return value, it leaves the required session_id undefined and offers no details about the page context or limitations. This is insufficient for correct invocation.
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 0%, and the description provides no parameter information. The required 'session_id' parameter is completely unexplained, and the optional 'page_id' is only vaguely hinted at by 'on the page'. This is a major gap for an agent trying to call the tool correctly.
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 states a specific verb ('Detect'), a clear resource ('currently logged-in username on the page'), and lists supported sites (Reddit, X, GitHub, HN). It also states the return value ('username' or 'unknown') and ties the tool to the commenting workflow, distinguishing it from page_comment and other siblings.
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?
There is clear usage guidance: 'Use before commenting to avoid duplicates.' This tells an agent when to invoke the tool. However, it does not explicitly mention when not to use it or provide alternative tool comparisons.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.