get_post_analytics

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

With no annotations, the description carries full burden. It discloses that it returns only published posts with platform post IDs and excludes certain accounts. It details Pinterest-specific metrics and rolling window behavior. No contradictions are present, though rate limits or authentication are not mentioned.

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 front-loaded with the main purpose and essential details. It is structured with clear sections for supported platforms and Pinterest extras, every sentence adds value without redundancy.

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 complexity (multiple platforms, varied metrics), the description is thorough. It explains what metrics are returned for each platform, highlights special cases (Pinterest 90-day rolling), and specifies exclusion rules. No output schema exists, so the description compensates well.

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 100% coverage, so the baseline is 3. The description adds value by explaining the meaning of return metrics and how platforms affect results, which indirectly informs parameter usage. It provides context beyond the schema descriptions.

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 identifies the tool's function: fetching published posts with performance metrics. It specifies supported platforms and exclusions, differentiating it from sibling tools like list_posts which only list posts without analytics.

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 explicitly states constraints (only published posts with platform post ID, excludes LinkedIn personal accounts) and lists supported platforms. Although it doesn't directly compare to alternatives, the context is sufficient for an agent to decide when to use this tool.

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