get_post_success_rate

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

The description marks the tool as read-only, which implies no destructive side effects. However, without annotations, it should provide more detail on data aggregation scope, whether results are cached, or if it enforces rate limits. The mention of 'rate' is vague.

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 brief and front-loaded with the core functionality. It communicates purpose in one sentence plus a read-only qualifier. The use of backticks around 'days' is slightly informal but not detrimental.

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?

While the description lists output fields (total, success, etc.), it does not specify the response structure or calculation of 'rate'. No output schema is provided, so the description should clarify these details. It is adequate but not fully complete.

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?

The single parameter 'days' is referenced in the description ('last ``days`` days') but adds no meaning beyond the schema's default, min, and max. With 0% schema description coverage, the description only minimally compensates by indicating the time range.

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 it is a roll-up of post outcomes including specific metrics (total, success, failed, dry_run, blocked, rate) and notes it is read-only. It is a specific function distinct from sibling tools like get_analytics_summary or get_daily_stats, though it does not explicitly differentiate.

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?

No guidance is provided on when to use this tool versus alternatives like get_analytics_summary or get_daily_stats. The description only explains what it does, not the context or prerequisites for invocation.

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