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

Annotations declare readOnlyHint=false, destructiveHint=false, openWorldHint=false, and the description adds the paid-plan gate plus the fact that the AI applies per-platform tone/limits. It does not clarify whether generated captions are persisted or merely returned, nor any rate limits — a gap given readOnlyHint=false hints at a write.

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 short sentences, front-loaded with the core action and scoped by the platform-optimization claim and the plan gate. Efficient with little waste, though the middle sentence is somewhat promotional.

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?

No output schema exists, so the description should ideally describe what is returned (e.g., one caption per platform). It covers the prerequisite but leaves the return shape and its relationship to downstream siblings like create_post_draft unstated.

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 prompt, platforms, and additionalContext are already documented in the schema. The description adds no syntax, format, or enum guidance beyond what the schema provides, so the baseline 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?

States a specific verb+resource: 'generate platform-optimized captions' using Socialync's AI. Clear what it produces, though it does not explicitly differentiate itself from siblings like create_post_draft or validate_post (generation vs. persistence vs. validation).

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?

Adds a real prerequisite ('Requires a paid plan; not available on the free plan'), which is useful when-to-use context. However, it gives no guidance on how this differs from siblings such as create_post_draft or when to prefer generating vs. drafting manually.

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