AnythingMCP

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

No annotations are provided. The description says 'Setup instructions,' suggesting an informational output rather than a live connection or mutation, but it does not explicitly state side effects or return format.

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 concise sentence with no fluff, and it includes the key enum values, making the tool's purpose immediately understandable.

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 instruction-retrieval tool with one enum parameter, the description is sufficient. It could mention what the instructions contain or how it relates to sibling tools, but those details are not essential.

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 schema already defines the client enum with a clear description. The tool description repeats the client list but adds no additional semantic detail beyond the schema.

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?

Clearly states the tool provides setup instructions for connecting a specific AI client to AnythingMCP, and the enumerated client list distinguishes it from sibling overview/get-started/list 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?

Implies use when the user needs per-client setup instructions, but does not explicitly contrast with get_started, overview, or list_connectors.

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 burden of behavioral disclosure. It conveys that this is instructional ('How to install and run'), but does not state whether the tool executes commands, returns static text/markdown, or has side effects. For a tool with zero annotation coverage, this is a significant gap.

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, efficient sentence with no filler. It front-loads the core value proposition (installation and running) and adds a time estimate for usefulness.

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, no-output-schema tool this is essentially the entire contract, yet the description is minimal. It does not state what the tool returns (e.g., step-by-step instructions, a link, or a command), which is the one thing an agent would need to know to use it correctly. Adequate but thin.

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 the description need not explain parameter meaning. Baseline 4 for a parameterless tool applies; nothing is missing here.

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 purpose: it provides installation/run instructions for an AnythingMCP gateway. It is distinguishable from siblings (connect_client, list_connectors, overview), which are operational actions rather than a setup guide. The phrasing is a how-to rather than a tautology, though it reads more like a title than a full purpose statement.

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?

No explicit guidance on when to use this tool versus its siblings. The context implies first-time setup (as opposed to overview, connect, or list), but this is left entirely to inference. There is no mention of alternatives or exclusions.

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 burden. The word 'Overview' suggests a read-only, non-destructive operation, but it does not explicitly state side effects or lack thereof. Reasonable transparency given the simple nature.

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, concise sentence that directly communicates the tool's purpose without unnecessary fluff.

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 list tool, the description is sufficient to understand its function. It could mention the output format, but the absence is not a significant gap given the tool's simplicity.

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 schema has no parameters, so coverage is complete by default. The description adds no parameter-specific details because none exist, resulting in the baseline score.

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 tool provides an overview of 175+ pre-built connectors and connector types, which is a specific and distinct purpose among the sibling tools (connect_client, get_started, overview).

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 does not explicitly state when to use this tool versus its siblings. It implies it is for listing connectors, but that guidance is not directly provided.

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.