get_threads_posts

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

No annotations are provided, so the description carries the full disclosure burden. It hints that only published (not draft) content is returned, but says nothing about auth requirements, pagination, ordering, or what a "thread" versus a "post" looks like in the response.

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?

One front-loaded sentence with no filler. However, hard-coding the handle @in.yogeshwar into the description is unusual and can mislead an agent into thinking the account is a fixed target rather than a contextual default.

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?

For a single-optional-parameter read tool with no output schema or annotations, the description is minimally adequate but leaves return shape and auth context unexplained. An agent knows what it fetches but not what it gets back.

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% and the single limit parameter is fully documented in the schema, so the description needn't repeat it. The description adds no interpretation of what counts as a "recent" thread, which is the one ambiguity the schema leaves open.

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 pairs a specific verb ("Fetch") with a specific resource ("recent published threads and posts") and narrows scope to one account. An agent can distinguish it from publish_threads_post or get_threads_insights, though it never explicitly contrasts with those siblings.

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?

There is no statement of when to use this versus the sibling read tools (get_threads_profile, get_threads_insights) and no exclusions or prerequisites. The only cue is the implied read-only nature of "Fetch ... recent published."

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