tc_link

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

With no annotations, the description fully discloses behaviors: batch returns failures-only by default, details:true includes all rows; resolve returns compact or verbose; auto-resolution of dot-form subfields. No contradictions.

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 dense and run-on, lacking paragraph breaks or bullet points. While information-dense, it could be better structured for quick scanning by an AI agent.

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?

Covers all actions and parameter behaviors thoroughly, including the 'discover→act→verify' loop for the 'links' action. No output schema exists, but description provides sufficient detail for effective use.

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?

Adds meaning beyond the schema by explaining parameters like 'a' as source, 'b' as destination, 'links' array structure, 'save' for batch, and 'details'/'verbose' for output control. Does not explicitly cover 'autoResolve' default but schema coverage is low, so description compensates well.

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 defines the tool's purpose: managing variable links (producer↔consumer) with multiple actions (link, unlink, resolve, links, batch variants). It distinguishes between single and batch operations, but could be more succinct about the core function.

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?

Explicitly advises batch usage for multiple links ('BATCH-FIRST'), explains when to use link_batch/unlink_batch instead of single actions, and describes behavior of unlink with only 'a'. Provides clear context for tool selection.

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