Get a post by ID

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, but the description adds genuinely new behavior: a single request with no automatic pagination, and that provider errors surface as failures even under HTTP 200. That error-semantics note is valuable and not derivable from the schema or annotations.

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?

Short and front-loaded, with the pagination and error semantics placed early. 'Current Buffer GraphQL post' is telegraphic and slightly cryptic, but no sentence is wasted.

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?

Covers the key call-shape facts an agent needs (single request, no auto-pagination, error surfacing) for a 5-parameter tool with no output schema. It is complete enough to call correctly, though it never clarifies the interaction between id/payload/payload_file beyond what the schema states.

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 id, fields, account, payload and payload_file, including the payload/payload_file mutual exclusion. The description's 'Use upstream fields to bound data' adds a mild hint about fields usage but no syntax or format detail 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?

States a specific verb and resource ('Get a post by ID') and clarifies the underlying source ('Current Buffer GraphQL post'). It does not, however, distinguish itself from near-siblings like get_posts, get_post_template, or get_aggregated_post_metrics, nor explain what a 'Buffer GraphQL post' is relative to those.

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?

There is no when-to-use / when-not-to-use guidance and no alternative tool is named, despite get_posts and get_post_template sitting right next to it. The sentence 'Use upstream fields to bound data' is parameter advice, not usage routing.

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