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

With no annotations, the description carries the full burden of explaining behavior, but it only provides an external docs URL, group, and billing credit. It does not disclose return format, pagination/cursor behavior, authentication needs, or side effects.

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 short and contains no redundant prose, but its brevity is due to under-specification. The external URL is front-loaded, yet the description lacks the structured behavioral and parameter information needed for effective use.

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?

Given 5 undocumented parameters, no annotations, and no output schema, this description is far from complete. It only points to external documentation, leaving an agent unable to select and invoke the tool confidently.

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 0% and the description adds no parameter details. Parameters like proxyUrl and resFormat are unexplained, and the relationship between userId and screenName is not clarified.

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 title 'Get Followers User Collection' provides a clear verb+resource, and the URL references get-followers-list, so an agent can infer the endpoint. However, the description text itself does not explain the behavior and does not distinguish it from siblings like followersListV2 or followersIds.

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 only says 'Group: follows' and gives billing information; it gives no guidance on when to use this tool versus related follower/following list tools. There are no exclusions, alternatives, or context indicators.

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