set_keyword_link

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

With no annotations, the description carries the full burden. It transparently discloses delivery activation timing, upsert behavior, and platform limitations ('Only Instagram delivers today'). It doesn't cover auth or rate limits, but the key behavioral traits are well communicated.

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 three sentences, each earning its place. It front-loads the purpose, then adds essential operational details without fluff or repetition of schema content.

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 tool's complexity (6 params, no output schema, no annotations), the description covers the most critical aspects: function, update behavior, scope, and platform limitation. It could mention return values or error cases, but overall it's sufficiently complete for an AI agent to invoke 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?

Although schema coverage is 100%, the description adds semantic value by explaining the media_id field (global vs single post) and the platform limitation. It also highlights the composite scope for the upsert behavior, which is not evident from the schema alone.

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 opens with a clear verb and resource: 'Map a keyword to a resource/destination link for DM automation.' This directly states the tool's function and distinguishes it from sibling tools like list_keyword_links and delete_keyword_link, which are read and delete operations respectively.

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 provides useful context on when to use this tool, including re-running for updates and the distinction between global and per-post rules via media_id. It doesn't explicitly name alternatives, but the sibling tool names make the CRUD role obvious, and the upsert behavior clarifies this is the create/update tool.

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