get_post_analytics

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

The description adds critical behavioral context beyond the readOnlyHint annotation: the tool searches a limited set of recent posts and returns a not-found note if absent. This fully discloses the workaround behavior.

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?

Two sentences with no filler. The first sentence lists all returned stats, the second explains the internal search limitation. Every word is useful and front-loaded.

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 single-parameter tool with no output schema, the description fully covers what to expect (list of stats fields), the search limitation, and the not-found behavior. It is sufficient for an agent to decide when to call.

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 schema covers the one parameter (post_id) with a basic description. The tool description adds context that the post must be published and that the search is limited to the 500 most recent posts, which aids correct usage.

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 the resource 'performance stats for a published post by ID'. It lists specific metrics (views, emails, etc.) and distinguishes from siblings like get_post (retrieves post content) and get_post_comments.

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?

Explicitly notes the limitation that Substack has no per-post endpoint and that it searches the 500 most recent published posts. This guides when to use (only for recent posts) and when not (if post not among recent 500). However, it does not name alternative tools for stats beyond that scope.

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