llmconveyors-mcp

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

With no annotations provided, description carries full behavioral disclosure burden. It successfully discloses 'No authentication required' and return format 'JSON with name and version fields'. Missing only explicit safety/destructiveness classification (though implied by 'verify' purpose).

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 each earning place: purpose, usage guidance, auth disclosure, return format, and sibling alternative. Logical front-loading with no waste.

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 simple health-check tool with no output schema, description fully compensates by documenting return structure. Accounts for all relevant context: auth requirements, sibling differentiation, and verification use case. Appropriate for tool complexity.

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. Per rubric baseline for 0 params is 4. Description correctly requires no parameter discussion.

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?

Description opens with specific verb 'Get' and clear resource 'LLM Conveyors API server name and version'. It also distinguishes from sibling 'health-check' by contrasting basic verification vs 'deeper diagnostics', clearly delineating scope.

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 ('verify the MCP server is connected and reachable before running other tools') and explicit alternative ('For deeper diagnostics, use health-check instead'), giving clear decision criteria between sibling health endpoints.

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