anythingmcp_list_connectors

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

The description adds value beyond annotations by detailing the output format (plain-text catalog), specific contents (categories, connector types, link), and reinforces the read-only nature. With annotations already providing readOnlyHint and idempotentHint, the description enriches behavioral understanding.

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 three sentences, front-loaded with key behavioral info, and every sentence provides useful information without redundancy. It is efficiently structured.

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 tool with no output schema, the description covers the return value (plain-text catalog with categories and link) comprehensively. It is complete for the tool's purpose of discovery.

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 input schema has no parameters (100% coverage, 0 params). The description doesn't need to add parameter information since there are none. Baseline for 0 parameters is 4.

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 'Returns a plain-text catalog of AnythingMCP's 175+ pre-built connectors grouped by category... plus the 5 connector types you can build with no code'. It identifies the specific verb and resource, and the content clearly distinguishes this from sibling tools like 'connect_client' or 'get_started'.

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 tool explicitly says 'Use this to discover available integrations before connecting a client', providing clear context for when to use it. While it doesn't explicitly state when not to use it or mention alternatives, the guidance is sufficient for an agent.

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