get_followers_page

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

With no annotations, the description must fully disclose behavior. It mentions 'low-cost' but doesn't explain what that means (e.g., rate limits, caching). It fails to note that the tool likely returns paginated results and how pagination works (e.g., using page_id). Critical behavioral traits like idempotency or data freshness are absent.

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. However, it sacrifices necessary detail for brevity. While it is structurally simple, it lacks the front-loading of key operational information that would help an agent.

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 moderate complexity (pagination) and the presence of an output schema, the description should at least outline the pagination mechanism and parameter roles. It fails to do so, leaving the agent to guess how 'page_id' relates to 'limit' and 'target'. The absence of parameter descriptions undermines completeness.

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?

The schema has 0% description coverage for its three parameters. The description adds no parameter-level information, leaving agents without essential context about 'target' (what format?), 'limit' (max page size?), or 'page_id' (how to obtain and use cursor?). This is a severe deficiency.

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 the tool retrieves a followers page for a profile, using the verb 'get' and specifying the resource 'followers page'. The 'low-cost' qualifier hints at operational characteristics but doesn't conflict with purpose clarity. While it doesn't explicitly differentiate from sibling tools like 'get_following_page' or 'search_profile_followers', the resource name implies specificity.

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 alternatives, such as other paginated retrieval tools (e.g., 'get_profile_publications_page'). There is no mention of pagination strategy, prerequisites, or exclusions.

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