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

Annotations already declare readOnlyHint and openWorldHint, so the description's job is supplementary; it does add the credit cost ('Costs 1 credit') and the public-data scope, both concrete traits not present in annotations. It stops short of saying what happens for private, suspended, or nonexistent handles.

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?

Three short sentences with no padding, and the returned-field list is packed efficiently. The leading 'Profile.' fragment merely restates the title and earns no place.

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?

There is no output schema, so the description usefully enumerates the returned fields, which is exactly what an agent needs. The remaining holes are error/edge behavior for non-public handles and the meaning of cache_max_age.

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 only 50% and the description says nothing about parameters. The handle parameter is well documented in the schema itself, but cache_max_age is undocumented in both places, and the description does not compensate for that gap.

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?

Names the resource (Threads profile) and enumerates the returned fields (followers, bio, bio links, avatar, verification), which goes beyond the bare title. It does not explicitly distinguish itself from siblings like threads_searchUsers or threads_userPosts, so an agent must infer the boundary.

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 implied: supply a handle or profile URL, get that profile. The word 'Public' hints at a scope limit, but there is no statement of when to use this versus threads_searchUsers (finding a handle) or threads_userPosts (fetching content).

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