get_following

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

Discloses pagination via next_cursor and a 200-profile limit, but does not mention read-only behavior, authentication needs, or rate limits. Without annotations, more transparency would be beneficial.

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, front-loaded with purpose and key constraints. No extraneous words, every sentence earns its 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?

Covers basic purpose and pagination, but lacks details on response structure, ordering, rate limits, or error conditions. Given no output schema and many siblings, more completeness would help.

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?

Adds value beyond schema by clarifying that one of username/user_id/user_link must be provided (though schema says no required) and explaining next_cursor usage. Schema coverage is 100%, so baseline is 3; the extra context elevates to 4.

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?

Description clearly states it lists accounts a user follows with a limit of 200 per page. However, it does not differentiate from similar sibling tools like get_followers or get_top_following, missing an opportunity for distinction.

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 explicit guidance on when to use this tool versus alternatives like get_followers. The description only implies usage for listing followed accounts; no when-not or alternative directions are provided.

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