get_post

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

The description discloses what the response includes (status, caption, media, target accounts), providing good behavioral insight. Since no annotations are present, the description carries the full burden, and it does so adequately. However, it does not mention any side effects or additional constraints.

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 a single, clear sentence with no filler. Every word contributes to understanding the tool's function.

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 simple single-parameter read tool with no output schema, the description sufficiently explains what the tool does and what is returned. It could mention that the output includes the full post object, but the listed fields cover the essentials.

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 single parameter 'id' with description 'Social post id.' The description adds 'by id' but no further detail on format or validation, so value beyond schema is minimal, establishing a baseline 3.

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 'single social post by id', listing the included fields (status, caption, media, target accounts). This distinguishes it from sibling tools like list_posts (list) and create_post.

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 that this tool should be used when you have a specific post id and need detailed information. However, it does not explicitly exclude cases or mention alternatives like list_posts for retrieving multiple posts.

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