AnythingLLM MCP Server

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

No annotations are provided, so the description carries full burden for behavioral disclosure. 'List available LLM providers' implies a read-only operation but doesn't specify whether this returns all providers, requires authentication, includes rate limits, or provides structured data. For a tool with zero annotation coverage, this leaves significant behavioral questions unanswered.

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, efficient sentence that communicates the core purpose without any wasted words. It's perfectly front-loaded and appropriately sized for a simple listing operation with no parameters.

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 parameterless listing tool with no output schema, the description provides the minimum viable information about what the tool does. However, without annotations or output details, it doesn't fully address what 'available' means, what format the list returns, or how this differs from related tools. The simplicity of the operation keeps it from being inadequate, but more context would be helpful.

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 with 100% schema description coverage, so the schema already fully documents the absence of inputs. The description appropriately doesn't mention parameters, maintaining focus on the tool's purpose without redundancy. A baseline of 4 is appropriate for parameterless tools.

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 clearly states the action ('List') and target resource ('available LLM providers'), making the purpose immediately understandable. It doesn't differentiate from siblings like 'list_agents' or 'list_workspaces', but the specificity of 'LLM providers' provides adequate clarity for this simple operation.

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 provides no guidance on when to use this tool versus alternatives. With siblings like 'update_llm_provider' and 'get_system_info' that might overlap in context, there's no indication of prerequisites, timing, or comparative use cases for this listing operation.

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