linkedin_profile_summary

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

No annotations are provided, so the description carries the full burden. It describes a get operation but lacks disclosure of behavioral traits such as read-only nature, authentication needs, or any side effects. The simple verb 'Get' suggests a read-only action but is not explicitly stated.

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 concise sentence that immediately conveys the core purpose. It is appropriately sized, though it lacks additional structural elements like bullet points or separate sections for clarity.

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 there is no output schema, the description should provide more details about the returned data structure. It mentions 'followers + post statistics' but omits specific fields or format, and does not clarify behavior when dateRange is omitted. The tool is relatively simple but the description is insufficient for an agent to fully understand the output.

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 coverage is 100%, providing descriptions for both platformId and dateRange. The tool description does not add additional meaning beyond the schema, such as how the dateRange affects the output or the format of the response.

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 retrieves a combined overview of LinkedIn profile followers and post statistics. This distinguishes it from sibling tools like linkedin_followers and linkedin_post_stats which focus on individual metrics.

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 implies usage for obtaining a combined summary, but it does not explicitly mention when to use it versus alternatives, nor does it provide context or exclusions.

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