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

No annotations are provided, so the description carries the behavioral burden itself. It usefully states that the tool is read-only and specifies the optional account scope, but it does not mention permissions, freshness, or rate-limit behavior.

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 dense sentence that front-loads the returned counters and ends with the optional account scope and read-only status. Every clause adds information without padding.

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?

For a small two-parameter stats tool with no output schema and no annotations, the description covers the key return metrics and the optional per-account behavior. It could go slightly further on return shape or whether counters are aggregate snapshots, but it is largely sufficient.

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 only 50% because account_id has no schema-level description, but the description compensates by saying the stats are optionally for one account. The required id parameter is also documented in the schema as a campaign UUID from list_campaigns.

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 states a specific retrieval target: LinkedIn counters for a campaign, with an optional per-account scope. It clearly distinguishes the resource from the broader campaign getters by enumerating LinkedIn-specific metrics, though it does not explicitly name sibling alternatives.

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?

It notes that stats can be requested for one account, which gives a basic usage cue for account_id. However, it gives no explicit guidance on when to use this tool versus get_campaign_analytics, get_campaign_live_status, list_campaign_linkedin_accounts, or sync_campaign_stats.

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