get_followers

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 mentions pagination and sorting behavior but does not explicitly state that this is a read-only operation (e.g., no side effects), authentication requirements, or rate limits. The behavior described is minimal.

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 two sentences, front-loaded with purpose, and includes only essential information (pagination and sort). No wasted words.

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?

With 3 parameters and no output schema or annotations, the description covers the basics but omits the return format (though implied). It also doesn't mention default per_page (80 from schema). Slightly incomplete for a tool with no output schema.

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 each parameter (page, sort, per_page) already described in the schema. The description adds no new semantics beyond restating pagination and sort by creation date, which matches the enum. Baseline 3 is appropriate.

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 verb 'get' and the resource 'followers' scoped to 'the authenticated user'. It is distinct from sibling tools like 'get_user_by_username' and 'get_authenticated_user', as it targets followers specifically.

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 implies usage for retrieving followers of the authenticated user but provides no explicit guidance on when not to use it or alternatives. Given the sibling tools, some are unrelated, but the description could mention that this does not retrieve followers of other users or lists.

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