get_profile_data_and_connection_u0026_follower_count

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

No annotations are present, so the description must convey behavioral traits. It fails to mention any side effects, authentication needs, rate limits, or data scope (e.g., whether it returns raw counts or processed data). The description is purely nominal.

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 extremely short but at the cost of being a tautology—it merely repeats the tool name. It does not earn its place by providing useful information; it is under-specified rather than concise.

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 high number of similar siblings and the lack of output schema, the description is woefully incomplete. It does not explain what data is returned, how it differs from 'get_profile_data' or 'get_profile_connection_u0026_follower_count', or any usage caveats.

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 input schema covers 100% of parameters and provides an example value for 'username'. The description does not add any additional meaning beyond what the schema already states, so 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 'Get Profile Data and Connection & Follower Count' restates the tool name almost verbatim and does not differentiate it from closely related siblings like 'get_profile_data' or 'get_profile_connection_u0026_follower_count'. It lacks specificity on what exactly is returned versus those tools.

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 over alternatives. With siblings that have overlapping names (e.g., 'get_profile_data_connection_u0026_follower_count_and_pos'), the agent has no way to decide which to invoke.

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