get_review_server_status

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

With no annotations, the description carries the full burden, and it does disclose an important ownership/security boundary: only verify a service owned by this MCP process and never adopt another listener. However, it omits whether the operation is read-only, what happens when the session is unknown, and other basic behavioral traits for a status-check tool.

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 sentence with no wasted words, but it is not front-loaded with a clear statement of what the tool does. The most informative part is the trailing constraint rather than the core action.

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?

Although an output schema exists and reduces the need to explain return values, the description still leaves the core action and the required session_id undocumented. For a tool with no annotations and 0% parameter coverage, this is not complete enough for reliable 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?

There is one required parameter, session_id, with 0% schema description coverage, and the description does not mention it at all. With the schema providing no semantic detail, the description fails to compensate for the parameter documentation gap.

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 says to 'Verify a service owned by this MCP process,' but it never states that this is the review server status tool or what 'verify' actually returns. The resource is referred to only as 'a service,' so the purpose remains vague despite the tool name.

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?

It provides a negative constraint ('never discover or adopt another listener') but gives no guidance on when to call this versus siblings like start_review_server, stop_review_server, or get_runtime_status. The description does not state prerequisites or appropriate contexts for use.

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