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

Annotations mark this as non-read-only, open-world and non-idempotent, and the description usefully adds that gtm.help never posts on the user's behalf — the human copies, edits and posts — which resolves the ambiguity of a write-shaped hint with no side effect on Reddit/LinkedIn/X. It also states the return payload (text plus exact link), adding value beyond the annotations.

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 tight sentences: purpose and inputs first, return value second, the no-auto-posting guarantee last. No filler, and the most decision-relevant information is front-loaded.

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, the description correctly compensates by naming what is returned (draft text and paste link). It leaves minor gaps — e.g., whether the draft is persisted or what happens on an invalid/stale opportunity_id — but nothing that would cause a misinvocation.

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 100%, so both parameters (opportunity_id and the tone enum with its four modes) are already fully documented in the schema. The description's mention of workspace writing settings is contextual rather than parameter-level guidance, so this is the baseline 3.

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?

Specific verb (write a reply) plus resource (one Reddit/LinkedIn/X opportunity) and the platform scope. It clearly separates itself from siblings like list_opportunities (the ID source) and update_opportunity (which mutates state), so an agent can pick it without opening another schema.

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 tells the agent where the opportunity_id comes from (list_opportunities) and what the tool's outcome is, giving clear trigger context. It does not name explicit when-not-to-use conditions or alternatives such as submit_play_draft, which keeps it 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.