get_post_analytics

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

With no annotations provided, the description carries full burden and does well by disclosing key behavioral traits: it returns real-time metrics across platforms, notes platform-specific latency (TikTok/YouTube 24-48h), and specifies a plan requirement (Premium). It doesn't mention rate limits or authentication details, but covers essential operational context.

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?

Three sentences with zero waste: first states purpose and metrics, second adds scope and behavioral notes, third specifies requirement. Each sentence earns its place, and information is front-loaded appropriately.

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 no annotations and no output schema, the description does well to cover purpose, behavioral traits, and requirements. It could mention the return format or structure, but for a read operation with good parameter documentation, it's mostly complete. The sibling context suggests this is adequately differentiated.

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 description coverage is 100%, so the schema already documents all parameters well. The description adds some value by implying the 'id' parameter is for a specific post and mentioning platforms in context, but doesn't provide additional syntax or format details beyond what the schema provides. Baseline 3 is appropriate.

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 verb 'Get' and resource 'engagement analytics for a specific post', listing specific metrics (likes, views, shares, impressions, comments). It distinguishes from siblings like 'get_post' (which likely retrieves post content) and 'get_social_analytics' (which might be broader).

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 provides clear context about when to use it (for post-specific engagement metrics) and mentions a prerequisite (Premium plan). However, it doesn't explicitly state when NOT to use it or name specific alternatives among siblings, though the context implies it's for analytics rather than content retrieval.

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