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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does disclose the 60-account limit and the return fields, which is useful. However, it does not explicitly state that the operation is read-only (though 'export' implies this), nor does it mention authentication requirements, rate limits, or any potential side effects. Given the lack of annotations, this is a moderate gap.

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?

The description is two sentences, front-loads the core action and limit, lists the return fields, and provides a concrete URL example. Every word earns its place with no redundancy or fluff.

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 simple tool with one parameter and no output schema, the description covers the purpose, the limit, the return fields, and an example. It does not explicitly mention prerequisites like authentication or clarify whether the 60-account cap implies truncation or pagination, but these are minor gaps. Overall, an agent can invoke it correctly with the given information.

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% since the single 'url' parameter already has a description with an example. The tool description reinforces the same example but adds no new semantic meaning beyond the schema. Thus, the baseline of 3 is appropriate; the description does not compensate for any coverage gap because there is none.

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 clearly states the tool exports up to 60 accounts a Threads user follows, and lists the specific return fields (usernames, display names, follower counts, verification status). It uses a specific verb and resource and implicitly distinguishes from siblings like export_followers (followers vs following) and export_profile (profile info).

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 explains what the tool does and provides an example URL, but it does not explicitly state when to use this tool over the sibling export_followers or other alternatives. There is no mention of 'use this to get who a user follows' or a directive to choose the follower tool for the reverse. The context is clear but the routing guidance is implied rather than explicit.

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