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

The description says remove:true apaga (deletes), but annotations declare destructiveHint=false, which means only additive updates. That is a direct contradiction even though the description otherwise adds useful auth, key-handling, and retry details.

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 but front-loaded: purpose first, followed by endpoint/auth, conversion identifier behavior, key handling, remove/test modes, and failure handling. It contains no filler, though several details are compressed into technical shorthand.

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?

With no output schema but with annotations present, the description covers auth, external endpoint, side effects, key redaction, remove/test behavior, and failure retry limits. It still omits the meaning of enabled and says less about how this relates to sibling lead-capture tools.

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 60%, and the description adds meaningful semantics for apiKey (public App Store key, not OAuth, only keyLast4 returned), remove (deletes), and sendTest (tagged guiaflow-teste conversion). It leaves enabled undefined and mentions conversion_identifier even though that is not an input property.

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?

States a specific action: connect an already-published permanent link to RD Station Marketing, and adds the concrete side effect that lead.created becomes a CONVERSION. This is much more specific than the sibling tool names and makes the resource clear.

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?

Implies a prerequisite (the link must already be published) and explains remove and sendTest modes. However, it never explicitly says when to choose this tool over related siblings such as set_lead_webhook or other lead-capture tools.

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