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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real behavioral value beyond that: it enumerates the returned content (blurbs with links, first-name-plus-initial reviews, hashtags, profile links) and states the mandatory brand rules (no part numbers, customer info, appointment times, or 'best' claims) that constrain any post built from it.

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?

It is a single dense sentence, but the most important framing — approved, ready-to-post material — comes first, followed by the content inventory and then the filter. The long parenthetical of brand rules is justified because those rules govern how the content may be used, though the sentence is heavier than ideal.

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 must describe returns itself, and it does: it names each content type plus the governing brand rules, which is what an agent needs to know before composing a post. It omits any note on volume, ordering, or what an empty topic match returns, but for a one-parameter read tool it is largely complete.

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% with a single optional 'topic' string, so the baseline is 3. The description earns above that by giving concrete example values ('dryer vent', 'refrigerator', 'Louisiana') that clarify the expected granularity of the filter beyond the schema's bare 'Optional topic to filter by'.

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 resource — approved Facebook/Instagram/Google post material (press blurbs, reviews, hashtags, profile links, brand rules) — so an agent can tell it apart from siblings like get_business_info or book_repair. It stops short of naming any alternative or explicitly contrasting its scope, but the content inventory is concrete enough to identify the tool's 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?

Usage is only implied: an agent infers it should call this when it needs approved social copy, and the topic filter is illustrated with examples ('dryer vent', 'refrigerator', 'Louisiana'). There is no statement of when not to use it, nor any pointer to a sibling tool for related needs.

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