get_post_details

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

The description adds useful behavioral context beyond the readOnlyHint annotation by mentioning the full comment tree and recorded engagement history from previous snapshots. This tells the agent that the tool returns historical data and nested comments, which is not evident from annotations alone.

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?

A single concise sentence that front-loads the core action and lists the key data categories without fluff. Every phrase earns its place.

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?

The description plus output schema and readOnly annotation cover the main use case, but the optional account parameter is unexplained and the max_comments behavior is ambiguous given the 'full comment tree' wording. These gaps prevent it from being fully complete for correct invocation.

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 0%, so the description needs to compensate, but it only loosely maps to post_id ('one post') and max_comments ('comment tree'). It omits any explanation of the optional account parameter, and 'full comment tree' conflicts with the max_comments default of 100, which could mislead an agent.

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 identifies the resource (one post) and the kind of result (metrics, full comment tree, engagement history). It distinguishes itself from list-oriented sibling tools by emphasizing a single-post deep dive, though 'deep dive' is slightly less explicit than a verb like 'retrieve'.

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?

'Deep dive on one post' provides clear context for when to use this tool: when an agent needs detailed, historical, single-post information rather than a broader feed or listing. It does not explicitly name alternatives or exclusions, but the context is clear enough to route selection.

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