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

No annotations are provided, so the description carries the full burden. It discloses that the payload is ready-to-post, within platform limits, and includes the imperative to 'Post verbatim; keep attribution.' This adds behavioral context beyond the schema (e.g., exact text usage, attribution requirement), but does not mention error handling or auth needs, which are likely minimal for a generation tool.

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 a single, front-loaded sentence that efficiently states purpose, lists platforms, enumerates output components, and gives an implementation directive. No wasted words or redundant phrasing.

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 should clarify the return structure. It lists components (text, hashtags, image, intent URL) but does not specify whether the output is a string, JSON object, or array, nor how the agent should extract and post each part. The instruction 'Post verbatim' clarifies the text usage but not the parsing or assembly of the payload. For a simple tool with 2 params, this is borderline adequate but leaves room for ambiguity.

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 100% for both parameters, so the baseline is 3. The description enriches the platform parameter by listing valid values and implies format constraints via 'within platform limits,' but does not add substantial meaning beyond the schema. The article_id is already well-described as sourced from asha_feed/asha_search_articles.

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 purpose: generate ready-to-post social share payloads for an article, listing explicit platforms and content components (text, hashtags, image, intent URL). This is a clear verb+resource combination that distinguishes it from siblings like asha_share_pack or asha_mint_share_link.

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 implies usage (when needing share payloads for an article) and includes a direct instruction to post verbatim and keep attribution, but it does not explicitly state when not to use this tool or mention alternatives such as asha_share_pack. Guidance on tool selection is missing.

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