get_network_stats

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool returns 'network size, growth indicators, and connection insights,' which gives some output context, but lacks critical behavioral details: it doesn't specify if this is a read-only operation (implied but not explicit), mention rate limits, describe data freshness, or note authentication requirements beyond 'authenticated user.' For a tool with zero annotation coverage, this leaves significant gaps in understanding how the tool behaves.

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 efficiently structured in two sentences: the first states the purpose and scope, and the second specifies the return values. Every word adds value, with no redundancy or fluff. It's front-loaded with the core function, making it easy for an agent to quickly grasp the tool's role.

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 tool's simplicity (0 parameters, output schema exists), the description is minimally adequate. It covers the purpose and output types, but lacks behavioral context (e.g., authentication needs, rate limits) that would be helpful even with an output schema. The presence of an output schema means the description doesn't need to detail return values, but it could better address when and how to use the tool in practice.

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 has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately avoids discussing parameters, focusing instead on the tool's purpose and output. This aligns with the baseline expectation for zero-parameter tools, where the description should not waste space on non-existent inputs.

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 tool's purpose: 'Get statistics about the authenticated user's LinkedIn network' specifies the verb (get), resource (network statistics), and scope (authenticated user's LinkedIn network). It distinguishes from siblings like 'get_profile_views' or 'get_my_post_analytics' by focusing on network-level metrics rather than profile or content analytics. However, it doesn't explicitly differentiate from all siblings (e.g., 'analyze_engagement' could overlap), preventing a perfect score.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., authentication status), compare to similar tools (e.g., 'analyze_engagement' for engagement metrics), or specify use cases (e.g., for network growth analysis vs. content performance). The absence of usage context leaves the agent to infer applicability from the purpose alone.

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