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

From the description, the tool returns 'setup instructions', indicating a read-only, informative behavior. No annotations exist, so the description carries the burden. However, it does not specify the output format or that it does not perform actual connections.

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?

Single sentence with no redundant words. Efficiently communicates core purpose and supported clients.

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?

Given the simple tool (1 param, no output schema), the description is adequate but could be improved by clarifying that the output is step-by-step instructions for each client. Currently ambiguous whether 'setup instructions' is the tool's action or its output.

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 only parameter 'client' is fully described in the schema with enum values and description. The tool description merely repeats the enum list, adding no new semantic information 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's purpose: to provide setup instructions for connecting specific AI clients to AnythingMCP. Lists five client options and distinguishes from siblings like 'get_started' and 'list_connectors'.

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 siblings. The description implies use for connecting clients, but does not contrast with 'get_started' (initial setup) or 'overview' (general info).

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