health

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

With no annotations provided, the description carries the behavioral transparency burden. It states the tool reports status (which reasoning model and tools are available), implying a non-mutating read operation. However, it does not explicitly state that it is read-only, lacks side effects, or mention any authentication or failure conditions. This is adequate for a simple status tool but lacks explicit reassurance.

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, front-loaded sentence that immediately states the action ('Show') and the subject ('Novelty MCP status'), then expands with two specific details. No wasted words.

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?

For a zero-parameter health check tool, the description is sufficient: it states what the tool reports and the context (status check). An output schema exists, so return values need not be described. It does not cover edge cases like failure responses, but for a health tool this is acceptable.

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 tool has zero parameters, and the schema coverage is trivially 100%. The description adds no parameter-specific semantics, but none are needed. Baseline for 0 parameters is 4.

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 uses the specific verb 'Show' and clearly identifies the resource: 'Novelty MCP status'. It further specifies the exact contents of that status (which reasoning model is wired in and the tools available), which clearly distinguishes it from sibling tools like recon or review_file.

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 implies usage for checking the health/configuration of the Novelty MCP server, but it does not explicitly compare to alternatives or state when not to use it. Given the sibling tools, no other tool serves a status-query purpose, so the usage context is clear but not explicitly stated.

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