Get post

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

Annotations already provide readOnlyHint=true and destructiveHint=false, so the safety profile is established. The description adds useful context about the response contents, but doesn't disclose operational behavior such as error handling, permission requirements, or rate limits. This is acceptable for a simple read-by-ID operation.

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 two efficient sentences with no filler. The core action and key output contents are front-loaded, and the usage guidance is a separate, clear second sentence.

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 read-only tool with one required parameter, full schema documentation, annotations, and a description that enumerates the response contents, everything an agent needs to invoke it correctly is present. There is no output schema, but the description compensates by summarizing the response scope.

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 fully documents the single parameter postId with 'The post ID.' Since schema description coverage is 100%, the description doesn't need to add parameter details, and it doesn't. This aligns with the baseline for full schema coverage.

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 a specific action—'Get a single post by ID'—and defines the scope by listing the types of details returned (platform statuses, labels, media files, recurring schedule info, metrics). This distinguishes it from sibling tools like list_posts and get_post_metrics.

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?

It explicitly says to use this tool 'when the user references one specific post by its ID,' which gives the agent a clear trigger condition. It doesn't explicitly contrast with sibling tools like get_post_metrics, but the guidance is sufficient for correct selection.

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