llmconveyors-mcp

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

With no annotations provided, the description carries the full disclosure burden. It successfully adds 'No authentication required' (auth behavior) and 'Returns a simple alive status' (return value disclosure, critical given no output schema exists). Could be improved by mentioning rate limits or what 'alive' means (HTTP 200 vs specific payload), but covers essential behavioral traits.

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?

Five sentences, each earning its place: (1) purpose definition, (2) usage context, (3) auth disclosure, (4) return value (compensating for missing output schema), (5) sibling differentiation. Front-loaded with the core verb, no repetition of structured metadata.

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 with no output schema, the description is complete. It compensates for missing output_schema by describing the return value ('simple alive status'), covers authentication requirements, and differentiates from sibling tools. No gaps remain for this complexity level.

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 has zero parameters (empty object). Per scoring rules, 0 params = baseline 4. The description implicitly confirms no inputs are needed by omitting parameter discussion, which aligns with the empty schema.

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 opens with a specific action (Check) and target resource (LLM Conveyors API process/aliveness). It distinguishes from sibling health-check by explicitly contrasting 'process is alive' vs 'dependency-level diagnostics', clarifying this is a liveness probe vs readiness/deep check.

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?

Explicitly states when to use ('lightweight heartbeat check in monitoring or retry loops') and explicitly names the sibling alternative for different use cases ('For dependency-level diagnostics, use health-check instead'). Also notes 'No authentication required' which informs invocation context.

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