Get LinkedIn Organization Follower Count

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

Discloses required scope (rw_organization_admin), error codes (403, 404), and follows annotations (readOnlyHint, idempotentHint). No contradictions; adds context beyond annotations.

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?

Description is well-structured with sections for introduction, scope, args, returns, examples, and error handling. Each sentence adds value, and the most critical information is front-loaded.

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?

Covers scope, parameters, return format, error codes, and usage examples. However, it omits potential details like rate limits or data freshness, but given the tool's 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?

The schema covers the single parameter with full description. The description repeats the same information (e.g., 'Numeric organization ID') without adding new meaning or clarification beyond the schema.

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 it retrieves the follower count for a LinkedIn organization. The verb 'get' and resource 'follower count' are explicit, and it distinguishes itself from siblings (e.g., linkedin_get_organization) by focusing solely on followers.

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?

Provides concrete usage examples and error handling scenarios. While it lacks explicit 'when not to use' guidance, the examples clearly illustrate appropriate contexts such as checking or comparing follower counts.

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