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

Annotations already indicate this is destructive and not idempotent. The description adds useful behavioral context by specifying exactly what is removed: a single LinkedIn profile URL from a manual exclusion entry, not the entire entry. This goes beyond the raw destructiveHint and clarifies the target of the mutation.

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 concise sentences with no filler. The primary action is front-loaded, and the two lookup instructions each serve a distinct purpose. 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?

For a simple destructive operation with two required parameters, the description covers the action, both required identifiers, and how to retrieve them. It does not describe the return value or error behavior, but with no output schema and a straightforward removal operation, the provided context is largely sufficient.

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 only 33%, with the two required parameters undocumented in the schema. The description compensates by explaining the role of importedLeadId as identifying the URL to remove and pointing to specific tools to find valid values for both required parameters. workspaceId is left to the schema, which already documents it.

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 action ('Remove'), the specific resource ('a LinkedIn profile URL from a manual exclusion entry'), and the key ('by its importedLeadId'). It distinguishes itself from related tools like campaignstack_list_manual_exclusion_urls and campaignstack_get_exclusions by naming them as lookup helpers rather than the removal operation.

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 explicitly tells the agent how to obtain the required identifiers: use campaignstack_list_manual_exclusion_urls to find importedLeadId values and campaignstack_get_exclusions to find exclusionId values. This gives clear, actionable usage guidance and routes the agent to the correct sibling tools.

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