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

Annotations declare destructiveHint=false but readOnlyHint=false, so the agent knows it is a non-destructive operation that is not a pure read. The description adds genuinely useful output-shape context — 'Each idea is a short seed, not a full draft' — which is not available anywhere else since there is no output schema. It does not disclose cost, latency, or why the tool is not flagged read-only.

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, zero filler, with purpose front-loaded before the usage trigger and the output caveat. Every sentence earns its place.

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 usefully characterizes the return shape as short seeds rather than drafts, and it covers the triggering context. Minor gaps remain around how platform or count affect the results, but nothing needed to call the tool correctly is missing.

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 all three parameters (topic, count, platform) are already documented, including the count default and the platform omission behavior. The phrase 'N distinct' loosely implies the count parameter, but adds no syntax or format detail beyond the schema. Baseline 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 and resource with scope: generate N distinct post ideas on a given topic. This is clearly distinguishable from siblings like improve_post and suggest_hooks, though it never names an alternative explicitly.

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?

Gives an explicit trigger ('Use when the user asks for ideas, angles, or different takes on the same subject'), which is more than implied usage. It lacks any when-not guidance or routing to close siblings such as suggest_hooks.

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