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 documents authentication requirements ('No authentication required'), return value semantics ('simple ready/not-ready status'), and operational scope ('all dependencies initialized'). It omits minor details like rate limits or idempotency guarantees, but covers the critical safety and behavioral context an agent needs.

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 efficiently cover purpose, usage context, authentication, return format, and sibling distinction without redundancy. Information is front-loaded with the core action, and every sentence provides distinct value. Length is appropriate for a simple health-check tool.

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?

Given the absence of an output schema, the description compensates by describing the return status ('ready/not-ready'). For a zero-parameter health endpoint, it covers prerequisites (auth), semantics (dependencies), and sibling differentiation sufficiently. A minor gap remains regarding the specific response structure (e.g., JSON keys), but overall completeness is strong 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 contains zero parameters (empty object). Per calibration rules, zero parameters earns a baseline of 4. The description appropriately does not invent parameter documentation where none exist, and the 100% schema coverage means no additional semantic clarification is required.

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 a specific verb ('Check') with explicit resource ('LLM Conveyors API readiness') and scope ('all dependencies initialized'). It clearly distinguishes from the sibling health-live with the explicit clause 'For process liveness only, use health-live instead', resolving potential ambiguity between the two health endpoints.

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 ('Use this in automation pipelines to wait for readiness before sending agent runs'), mentions prerequisites ('No authentication required'), and explicitly names an alternative tool for a related use case ('use health-live instead'), covering both positive and negative guidance.

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