tgtrack_set_outbound_link_params

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

With no annotations, the description carries the full burden. It does not disclose any behavioral traits such as whether the operation is destructive, requires authentication, or has rate limits. It only lists parameters, leaving the agent uninformed about side effects or constraints.

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 very concise (one sentence) and front-loads the key terms. It could be slightly longer to cover missing parameters, but it is not verbose.

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 5 parameters, no output schema, and no annotations, the description is incomplete. It fails to explain the required linkID, the optional unsubscribedText, and the behavior of checkSubscription. The agent lacks critical context for correct invocation.

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?

Schema description coverage is low (20%). The description adds meaning for three of the five parameters (targetUrl, button text, check subscription) but omits linkID (required) and unsubscribedText. This partial coverage does not fully compensate for the schema's lack of descriptions.

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 states it sets outbound link parameters (button under post) and lists targetUrl, button text, and subscription check. This clearly indicates the tool's purpose and differentiates it from sibling tools like tgtrack_delete_outbound_link or tgtrack_set_link_name. However, it could be more explicit about the action (e.g., 'update or set these parameters').

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 usage guidelines are provided. The description does not mention when to use this tool vs alternatives, or any prerequisites or exclusions. The agent is left to infer usage from the name and parameter list.

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