Get Number of Followers

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

With no annotations, the description carries the full burden of behavioral disclosure. It implies a read operation via the verb 'get' and lists the returned metrics, but does not explicitly state that it is read-only, discuss rate limits, authentication requirements, or error behavior. The description is not misleading but adds limited depth beyond the obvious.

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, efficient sentence that front-loads the primary action and includes the key returned values. There is zero waste, and it is appropriately sized for a simple one-parameter read tool.

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 simple metric tool with one parameter and no output schema, the description covers the core purpose and return values. It could mention behavior when data is missing or clarify that it is account-level data, but given the simplicity, it is largely complete.

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%, so the date parameter is already well-documented in the schema (format, timezone, example). The tool description adds no additional meaning about the parameter, so it does not go beyond the baseline for high coverage.

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 states a specific verb (get) and resource (number of followers for the LINE Official Account) plus a temporal qualifier (on a specified date). It also lists what it returns (follower count, targeted reaches, blocks), which distinguishes it from sibling tools like get_follower_ids that focus on IDs rather than counts.

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?

There is no guidance on when to use this tool versus alternatives such as get_follower_ids or get_statistics_per_unit. The description does not mention exclusions or contexts where another tool would be more appropriate, leaving the agent to infer from the name alone.

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