generate_social_posts

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states what it generates and the supported formats; it does not disclose whether it returns output, executes side effects, requires any auth/preconditions, or how the generation behaves. For a content-generation tool this is a thin profile.

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?

Two sentences with no filler, and the core purpose is front-loaded. Efficient, though it could spare a few words to instead capture more behavioral detail without losing clarity.

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 6 parameters, 0% schema coverage, no annotations, and no output schema, the description is under-equipped. It does not explain the expected return value, how format interacts with platform, or what 'multi-format content' concretely produces. An agent needs more to call this correctly.

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 0%, so the description must compensate. It does partially: 'platform-specific' maps to the platform enum and 'threads/single posts/multi-format' maps to the format enum. However, it adds nothing about tone, length, or hashtags, which are left to the schema alone — partial compensation only.

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?

States a specific verb ('Generate') and resource ('platform-specific social media posts') and lists the four supported platforms. Mentions threads, single posts, and multi-format content. However, it does not explicitly differentiate from siblings like generate_creatives or generate_seo_content, which could overlap in purpose.

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?

No guidance on when to use this tool versus alternatives. The description never names sibling tools (schedule_content, generate_creatives, generate_seo_content) or states exclusions. The use case is only implied by the phrase 'social media posts,' leaving the agent to infer when this tool is the right choice.

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