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

Annotations already signal idempotent, non-read-only, and non-destructive behavior, and the description adds behavioral detail beyond that: it provisions an agent, states that re-sourcing is a no-op, and requires a connected LinkedIn account. It does not contradict the annotations. It omits cost/reversibility details, but the core side effect and prerequisite are disclosed.

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?

Three dense sentences, each earning its place: the core behavior, idempotent no-op behavior, and prerequisite/ID lookup routing. It is front-loaded and contains no filler.

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 2-param action with annotations and no output schema, the description gives enough to invoke correctly: required ID source, LinkedIn prerequisite, and side-effect/no-op behavior. The notable gaps are the undocumented workspaceId and no indication of what the tool returns, but the invocation path is clear.

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 coverage is only 50%: junctionId is documented in the schema, but workspaceId has no description. The description mainly repeats that junction IDs come from campaignstack_list_lead_magnet_posts without adding new semantics for either parameter, and it does not compensate for the undocumented workspaceId.

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 specific action, 'Source a magnet candidate', then defines it concretely: it provisions a post-engagement signal agent so commenters become leads. This clearly differentiates it from sibling tools like campaignstack_discover_lead_magnets, campaignstack_list_lead_magnet_posts, and campaignstack_dismiss_lead_magnet_post.

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?

It gives clear context: use this when you want to source a lead-magnet post and turn its commenters into leads, and it routes the agent to campaignstack_list_lead_magnet_posts for junction IDs. It also states the LinkedIn-account prerequisite. It does not explicitly say when not to use it or name alternative actions such as discover/dismiss, so it stops short of a 5.

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