llmconveyors-mcp

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

With no annotations provided, the description carries full disclosure burden. It successfully notes 'No authentication required' and details the return payload contents (status, uptime, version, dependency checks, memory usage), providing necessary operational context. Could marginally improve by explicitly stating the read-only/safe nature, though this is strongly implied by 'health check'.

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?

Four sentences efficiently structured: (1) core function and return values, (2) usage context, (3) authentication requirements, (4) sibling alternative. Every sentence adds unique value without repetition of structured schema data.

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 diagnostic tool without output schema, the description is complete. It enumerates the complete return data structure (status, uptime, version, dependencies, memory), distinguishes from related health endpoints, and discloses auth requirements—all critical context for invocation decisions.

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?

Input schema contains zero parameters. Per scoring rules, 0 parameters establishes a baseline score of 4. The description correctly omits parameter explanation since none exist, requiring no additional compensation.

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 specific verbs ('Run a detailed health check') and identifies the exact resource (LLM Conveyors API). It explicitly distinguishes itself from sibling tool 'health-live' by contrasting 'detailed' vs 'simple alive/dead check' and directing users to the alternative for simpler needs.

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?

Provides explicit when-to-use guidance ('diagnose connectivity or performance issues before retrying failed tool calls') and explicitly names the alternative tool ('For a simple alive/dead check, use health-live instead'), creating clear decision criteria between the two health endpoints.

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