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

The description discloses important side effects beyond the annotations: it costs credits plus a LinkedIn read action, changes the entry to PROCESSING, and later returns it to PENDING_REVIEW with a new draft. It also clarifies that retry alone does not re-fetch the page, adding meaningful behavioral context.

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 compact and every sentence earns its place: purpose, when to use it, why the alternative is insufficient, cost, and state transition. It is front-loaded with the core action and then provides necessary supporting detail.

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 two-parameter action tool, the description covers what the tool does, when to use it, what it costs, how it changes the entry state, and where the needed link details come from. Nothing essential is missing.

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?

The schema provides no descriptions for entryId or workspaceId (0% coverage). The description refers to 'the pending draft' and 'per entry', so entryId can be inferred as the pending review entry ID, but workspaceId is not explained at all. Some meaning is added, but the description does not fully compensate for the missing schema documentation.

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 a specific action: re-open the shared link and rewrite the pending draft based on the page's actual content. It clearly distinguishes itself from campaignstack_retry_review by explaining the exact scenario in which it should be used.

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?

Explicitly states when to use this tool instead of campaignstack_retry_review: when the draft answers a message containing a link and appears not to have seen the page. It also explains why retry is not a substitute, since retry reuses stored content and never re-fetches.

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