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

The description indicates the tool returns setup instructions rather than performing an actual connection, which clarifies its non-mutating nature. However, with no annotations provided, it does not explicitly disclose whether any side effects occur or what the output format will be, though the simple nature of the tool mitigates this 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?

The description is a single, front-loaded sentence that directly conveys the core purpose. It avoids unnecessary details and is appropriately concise for a tool with one parameter.

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 description gives a general overview but lacks specifics about the content of the setup instructions, such as whether they are step-by-step or include troubleshooting. With no output schema and no annotations, an agent may not know exactly what to expect as a return value, but the simplicity of the tool keeps it minimally complete.

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 already provides a complete description of the 'client' parameter with an enum listing all valid options. The description merely reiterates the enum values in parentheses, adding no extra semantic meaning beyond what the schema states.

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's purpose: providing setup instructions to connect a specified AI client to AnythingMCP. It enumerates the supported clients, making it distinct from siblings like get_started or overview, which have broader or different focuses.

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 usage context is implied: an agent would use this tool when asked how to connect a specific AI client to AnythingMCP. However, there is no explicit guidance contrasting it with sibling tools like anythingmcp_get_started or anythingmcp_overview, nor any 'when not to use' statements.

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