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

No annotations are provided, so the description carries the burden. It discloses that the tool costs 160 credits, a key behavioral fact, and clarifies that it returns text rather than performing an actual LinkedIn post. This is transparent for a content generation tool, though it does not mention side effects or rate limits, which are less critical here.

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 concise: two sentences (or three short statements) covering purpose, output, and cost. Every clause earns its place, with no fluff or redundant information.

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?

Without an output schema, the description properly explains the return value: 'Returns full post text, hashtags, and opening hook.' Given the simple parameter set (3 params, all described) and no nested objects, the description is complete enough for an agent to understand what the tool does and what it produces.

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%, and the schema already describes each parameter with meaningful details (e.g., language enum with formal Arabic clarification). The description does not add additional parameter semantics beyond what the schema provides, so the baseline score of 3 applies.

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 clearly states the tool's function: 'Write a professional LinkedIn post in formal Arabic (فصحى) or English.' The verb 'write' and resource 'LinkedIn post' are specific, and it distinguishes itself from sibling tools like write_copy or marketing_ideas by focusing on LinkedIn-specific content. It also mentions the output components (full post text, hashtags, opening hook), making the purpose unmistakable.

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 implicitly indicates when to use the tool: when a LinkedIn post is needed, with language choices (Arabic or English). However, it does not explicitly compare with alternatives or state when not to use it, though the context is clear enough for an agent to select it appropriately.

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