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

Beyond the readOnly/destructive annotations, it discloses what data is fetched (lead profile, campaign context, ICP data), the AI-generation behavior, the addDmHint conditional output, and crucially clarifies that the tool does not post the reply itself—the agent must use browser_* tools afterward. This prevents a false expectation of direct side effects.

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 sentences, with the core purpose front-loaded and each sentence providing distinct value: outcome, conditional behavior, and required follow-up actions. No filler or repetition.

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 zero-parameter tool with no output schema, the description covers what it does, how the result is produced, the shape of the returned data (replyText), and the exact next steps. Nothing necessary for correct invocation 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 input schema has zero properties, so schema coverage is vacuously complete and no parameter documentation is required. The description's mention of addDmHint is a contextual condition rather than a callable argument, though a brief note that it is not an input parameter would remove ambiguity.

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?

Opens with a specific verb+resource: 'Generate a contextual threaded reply for a LinkedIn comment.' The phrase 'threaded reply' plus the described workflow (find the comment, click Reply) clearly distinguishes it from top-level commenting siblings such as campaignstack_comment_on_post or campaignstack_craft_comment.

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 gives clear context: this is for replying to an existing LinkedIn comment, shows the conditional DM-nudge behavior, and specifies the follow-up browser actions. It does not explicitly name alternative tools or when-not-to-use conditions, so it falls just short of top-tier routing guidance.

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