get_following_page

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

No annotations are provided, so the description carries the full burden. It only says 'get', implying read-only, but no details about authentication, rate limits, or side effects. The pagination behavior (e.g., cursor-based) is not explained.

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 a single concise sentence, but it is too minimal. Every word is necessary, but it omits important context. A bit more structure would improve it without losing conciseness.

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 the tool's pagination and the existence of an output schema, the description should at least mention pagination mechanics or cursor usage. It also lacks any reference to authentication or rate limits, which are important for a data retrieval tool.

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 explanation for parameters. It does not clarify what 'target' is (profile identifier), how 'limit' caps results, or how 'page_id' drives pagination.

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 it retrieves a single page of following accounts for a profile. It uses specific verbs ('Get') and resources ('following accounts'), and distinguishes from siblings like 'get_followers_page' (which gets followers) and 'search_profile_following' (which searches).

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 on when to use this tool versus alternatives. For example, it does not mention that for multiple pages, one should paginate using the page_id parameter, or that for searching use 'search_profile_following'.

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