post_stats

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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering safety. The description adds behavioral context by stating it 'Returns all matching snapshots,' implying no pagination, and mentions trend visualization and filtering support. This goes beyond what annotations provide.

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 that are clear and front-loaded. The first sentence states the core purpose, the second adds value about returns, and the third notes filtering options. Minor redundancy ('Get stats snapshots' vs 'Returns all matching snapshots'), but overall efficient.

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?

With no output schema, the description should ideally explain the return format or stats fields. It only vaguely mentions 'trends over time'. The description adequately covers the input and basic behavior but lacks detail about what data is returned, leaving some gaps for a complex tool.

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. The description mentions filtering by profiles/networks and timespan, but does not add new meaning or clarify parameter format beyond the schema.

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 specific verb ('Get') and resource ('stats snapshots for one or more posts'), clearly stating what the tool does. It distinguishes from siblings like 'profiles_stats' by mentioning filtering by profiles/networks and timespan, which is unique to this tool.

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 implies usage (when you need stats trends over time) but does not explicitly state when to use this tool versus alternatives like 'profiles_stats' or 'history_list'. No exclusions or when-not-to-use guidance is provided.

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