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

Annotations already communicate read-only and non-destructive behavior; the description adds meaningful context by saying the data is 'raw' and that the metric set is 'platform-specific'. It does not cover auth expectations, rate limits, or return structure, but this is a simple read-only tool.

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?

One front-loaded sentence with no wasted words: 'Return raw analytics' states the action immediately, and each clause adds relevant scope or behavior.

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 two-parameter read-only tool with annotations, the description is mostly complete: it identifies the resource, granularity, lifecycle state, and platform-dependence of results. The main missing piece is explicit differentiation from sibling analytics tools and a little more parameter-level detail.

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?

Input schema has 0% property descriptions, so the description must compensate. It gives targetId useful meaning ('single published platform target') and clarifies that platform changes the metric set returned. Still, it does not explain how to obtain/format targetId or what the metric sets contain.

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 uses a clear verb ('Return') and a specific resource ('raw analytics for a single published platform target'). It implies distinction from account-level and multiple-post siblings via 'single' and 'platform target', but it does not explicitly name or compare 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?

The phrase 'published' and 'single' provides useful context: this tool is for one already-published platform target, not for drafts, account analytics, or bulk listing. However, it stops short of explicitly stating when-not-to-use or pointing to sibling tools such as get_accountanalytics or get_posts_with_analytics.

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