AnythingMCP

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

No annotations are provided, so the description carries the full behavioral burden. It is ambiguous whether this tool merely returns documentation ('Setup instructions') or actually performs a connection, despite the imperative name 'connect_client'; it also says nothing about auth requirements or what the response contains. That ambiguity is a real gap for a tool whose name implies an action.

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?

One front-loaded sentence with no filler. The parenthetical client list partially duplicates the enum in the schema, which is mild redundancy but also readable reinforcement.

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?

The tool is simple (one enum param, no output schema), and the description covers the basic intent. It still leaves the return value ('instructions' — text? links? steps?) and the read-vs-write nature unspecified, which the schema and absent annotations do not resolve.

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?

There is a single parameter with 100% schema coverage and an enum whose per-value description is already supplied by the schema. The prose enumeration of clients duplicates the enum rather than adding new semantics, so the description neither helps nor harms beyond baseline.

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 states a clear resource and outcome: setup instructions for connecting an AI client to AnythingMCP, and enumerates the supported clients. It does not, however, distinguish itself from siblings like anythingmcp_get_started or anythingmcp_overview, which an agent might reasonably confuse it with.

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?

Usage is implied — call this when you want to connect a specific AI client — but there is no explicit when/when-not guidance and no mention of the sibling tools (get_started, overview) that cover adjacent goals. An agent has to infer which of the four informational tools to pick.

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

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

With no annotations, the description carries the transparency burden. 'How to install and run' suggests an instructional/informational behavior rather than a mutating operation, but it does not state whether the tool returns instructions, starts a process, or has side effects.

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 focused sentence with no filler, and the main purpose is front-loaded. It could benefit from clarifying what the returned content looks like, but it is appropriately terse.

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 no-argument getting-started tool, the description supplies the key context (self-hosted setup, Docker). Since there is no output schema, mentioning the output format would make it more complete, but the tool is simple enough that the current description likely suffices.

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, so there is no parameter documentation burden. The description needs no parameter-level detail.

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 identifies a specific action and resource: installing and running one's own AnythingMCP instance via Docker. It goes beyond a tautology, though it does not explicitly contrast with sibling tools.

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 phrase 'your own AnythingMCP instance' implies the tool is for self-hosting/setup use cases, but there is no explicit when-to-use guidance or mention of alternatives such as connect_client or overview.

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

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses almost nothing: it does not say whether this is a read-only listing, whether results are paginated or static, whether auth is required, or what shape the response takes. The only behavioral hint is the fixed count of 522 connectors.

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?

A single tight sentence with no waste. However, the front-loaded phrase 'Overview of' is the weakest possible framing for a list tool and spends the most prominent position on a word that muddies the purpose.

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 tool with no output schema, the description needs to stand in for the return values, and it only gestures at them ('connectors and connector types'). It is enough to attempt a call but not enough to predict what an agent will receive.

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 takes zero parameters, so the baseline of 4 applies — there is no parameter semantics for the description to add. Nothing is missing or misleading in this dimension.

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 names the resource (522 pre-built connectors plus connector types you can build), so an agent can roughly infer this enumerates connectors. But the verb is vague — 'Overview of' could be mistaken for a summary document rather than a list, and that word collides directly with the sibling anythingmcp_overview, leaving the boundary between the two tools unclear.

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?

There is no when-to-use guidance, no condition distinguishing it from anythingmcp_overview, anythingmcp_get_started, or anythingmcp_connect_client. The agent is left to infer that this is the discovery step before connect_client.

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

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

No annotations are present, so the description bears the responsibility for behavioral disclosure. It does not state whether the tool is read-only, whether it fetches remote data, or if it has any side effects. While 'overview' implies a non-mutating operation, the lack of explicit transparency leaves the agent without clear expectations.

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, well-structured sentence that front-loads the main topic (AnythingMCP overview) and briefly covers the other key points (demo endpoint, learning resources). It is concise, clear, and contains no unnecessary words.

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 overview tool, the description is sufficiently complete: it tells the agent what the overview contains (what AnythingMCP is, what the demo endpoint does, where to learn more). It does not specify the output format, but given that no output schema is defined and the tool's scope is introductory, this is not a significant gap.

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 is empty (0 parameters), so the description does not need to explain parameter semantics. According to the rubric, 0 parameters yields a baseline of 4. The description adds no parameter-related information, but none 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 clearly states that the tool provides an overview of AnythingMCP, the demo endpoint, and learning resources. It names the specific resource and implies the action of giving an overview, distinguishing it from sibling tools like connect_client or list_connectors. However, it lacks an explicit verb like 'returns' or 'provides', making it slightly less immediate in conveying the action.

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 implies usage by stating what the overview covers, but it does not explicitly say when to use this tool versus the alternatives (e.g., get_started, list_connectors). There is no mention of when not to use it or how it relates to other tools, leaving the selection rationale to the agent's inference.

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