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

With no annotations provided, the description carries the behavioral burden. It discloses the export limit, the exact returned fields, and the required URL format. It stops short of mentioning auth, rate limits, or failure cases, but for this simple export tool the core behavior is transparent.

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?

Two sentences with no filler: the verb and resource are front-loaded, and every clause adds useful information—the cap, returned fields, and URL format.

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?

Since there is no output schema, the description compensates by naming the return fields. It fully specifies the single required parameter and its format. Minor contextual gaps exist around public-profile requirements or edge cases, but nothing essential for calling the tool 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 coverage is 100% and the schema already documents the url parameter with the same example. The description's URL reminder adds little semantic depth beyond what the input schema already provides.

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 opens with an explicit action (Export), object (followers), source (Threads user profile), and a concrete cap (up to 60). It also lists the returned fields, making it clearly distinguishable from siblings like postcopilot_export_following and postcopilot_export_profile.

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?

It clearly tells the agent what input to provide—a Threads profile URL—and gives an example format. It does not explicitly name alternatives or exclude cases, but the follower-specific wording provides sufficient routing context.

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