get_analytics_summary

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

With no annotations, description fully discloses read-only behavior and that it avoids LinkedIn API calls. It implies aggregation without side effects, which is transparent for a read operation.

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?

Two sentences with zero wasted words. Front-loaded with purpose and key differentiator, followed by behavioral note. Highly efficient.

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?

No output schema provided, and the description only hints at return values (success rate, quota, etc.) without detailing format. Parameter is missing explanation. For a simple tool, it's adequate but not fully self-contained.

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 has one parameter 'days' with default 30 and range, but description mentions none. Since schema coverage is 0%, description fails to add meaning to the parameter, leaving agents uninformed about how to set the time window.

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?

Description clearly states it's a one-call roll-up for analytics, listing specific metrics (success rate, quota, top hour, weekday). It distinguishes from sibling tools like get_daily_stats, get_post_success_rate, etc., by aggregating them into a single call.

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?

Description explicitly notes it's read-only and makes no LinkedIn calls, providing clear context for when to use. However, it does not explicitly state when not to use or list alternatives, though sibling tools serve as alternatives.

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