get_post_analytics

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

No annotations are provided, so the description carries the full burden. It implies a read-only operation ('Retrieve') but does not explicitly state that it has no side effects, nor does it mention authentication requirements or potential limitations (like 'recent' definition). It adds some context by listing metrics and the parameter, but it's not fully transparent for a tool with no annotation support.

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 highly concise—two sentences. The first states the main purpose, and the second details the only parameter. There is no redundant information, and it's front-loaded with the core functionality.

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 simple tool with one parameter and an output schema, the description covers the essentials: what it does, scope, and parameter details. It could be more explicit about what 'recent' means or any auth prerequisites, but given the simplicity and the availability of an output schema, it's largely complete. A minor gap in defining 'recent' prevents a 5.

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 0%, so the description must fully explain the parameter. It does so clearly: 'limit: Maximum number of recent posts to analyze (default: 5, max: 15).' This adds meaning beyond the schema by specifying the purpose, default, and maximum value, which is exactly what the agent needs.

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 'Retrieve' and the resource 'engagement metrics (impressions, reactions, comments, reposts) for recent posts authored by your account.' It specifies what metrics are included and the scope (own account, recent posts), making it distinct from sibling tools like get_feed or get_profile_views.

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 the tool (when you need engagement metrics for your recent posts). It doesn't explicitly contrast with alternatives or mention situations to avoid, but given the narrow scope, it's reasonably clear. It lacks explicit exclusionary guidance, hence a 4 rather than 5.

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