get_user_followings

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

No annotations provided, so description carries full burden. It discloses pagination via cursor but omits other behavioral traits like authentication requirements, rate limits, or behavior for private accounts. The statement 'with full profile metadata' is vague.

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 action, second sentence adds usage context. Every sentence is necessary and succinct.

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 3 parameters and no output schema, description covers core purpose, pagination, and a use case. Missing details on return format (what fields 'full profile metadata' includes) but adequate for basic understanding.

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%, each parameter already well-documented. The description adds no new parameter-specific meaning beyond the schema; the 'interest graph' context is tangential to parameters.

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 verb 'Fetch' and resource 'accounts a user follows' clearly state the action. It includes 'with full profile metadata' to specify output. Distinguishes from siblings like get_user_followers (followers vs followings) and get_user_info (single user info).

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?

Explicitly says 'Use this to map a user's interest graph' with reasoning. Provides clear context but does not explicitly mention when not to use it or compare alternatives, though the context implies appropriate use.

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