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

With no annotations, the description carries the full behavioral burden. It implies a read/collection operation and that only public group content is returned, which is useful, but it omits auth requirements, rate limits, whether collection is synchronous, and pagination behavior.

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?

A single efficient sentence with the key constraint (public Facebook Group posts) front-loaded. No padding or redundancy, though it is arguably too terse given the tool's complexity.

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?

An output schema exists so return values need not be described, which helps. But for a nested, five-field collection tool with zero annotations, the description leaves the 'approved URLs' precondition and the operational behavior unexplained, making it only minimally adequate.

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 the schema itself documents the nested payload fields. The description only adds 'approved URLs', mapping loosely to the urls array, and offers no meaning for limit, offset, results_limit, or only_posts_newer_than beyond what the schema already conveys.

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 ('Collect') and resource ('public Facebook Group posts'), and the platform implicitly distinguishes it from social-reddit-search and social-linkedin-search. However, 'approved URLs' is left undefined, so the exact input contract is not fully clear from the purpose statement alone.

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 gives no when-to-use guidance, no conditions that select this tool over its social-* siblings, and no explanation of what makes a URL 'approved'. The only hint at a precondition ('approved URLs') is stated without elaboration.

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