List publish targets

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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds context beyond those by explaining it connects to downstream servers, reads what is available, and changes nothing, plus details the LNKZ_MCP_TARGETS configuration format. It does not mention potential failure modes or latency, but it adds meaningful behavioral context.

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?

Two concise sentences, with the primary action stated up front and configuration details following. No filler or redundancy; every sentence earns its place.

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 zero parameters, no output schema, and annotations covering read-only behavior, the description adequately explains the tool's function, configuration, and side-effect-free nature. It could optionally describe the output format, but that is not critical for an agent to invoke it correctly.

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 there is nothing for the description to explain. The baseline for 0 parameters is 4, and the description correctly avoids inventing parameters. It does not need to compensate for any schema gaps.

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 connects to configured downstream MCP servers and lists the tools they expose, marking potential writes. This is a specific verb+resource (list tools on downstream servers), but it does not explicitly differentiate from sibling tools like list_connectors, so it misses the top score.

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 as a discovery-only read operation ('This is discovery only') but does not provide explicit when-to-use guidance or contrast with alternatives like list_connectors or prepare_publish. It leaves the agent to infer when this tool is appropriate.

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