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

With no annotations provided, the description carries the full burden, yet it discloses nothing about behavior, auth requirements, rate limits, or what the endpoint returns. The only transparency is billing cost and group membership.

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 but not usefully so — it's under-specified rather than concisely informative. The only real content is billing information, which is out of place as a primary purpose statement.

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 tool with no annotations and no output schema, the critical semantics (e.g., that this returns users whom a given profile follows) are entirely missing. Sibling tool names suggest a followers/following distinction that is never clarified.

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% with descriptions for all three parameters, including a helpful cursor explanation and a user_id example. Per the rubric, with high coverage the baseline is 3, and the description adds nothing beyond what the schema already documents.

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 'v2 / Profile Following Group: v2 / Profile' merely restates the tool's title and group membership without stating a function. No action verb or resource is mentioned, only the tool name 'get_' hints at retrieval, and the billing note is operational, not functional.

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?

No guidance is provided on when to use this tool versus its many siblings. There's no mention of when to prefer this over get_v2_profile_followers, get_v2_profile_feed, or other v2 profile tools, and no exclusions or prerequisites.

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