fb_get_post

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states that the tool retrieves post details, but it does not mention what fields or structure will be returned, whether authorization is required, how errors are handled, or any side effects. For a read operation this is minimal but still leaves the agent guessing about observable 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?

The description is a single clear sentence with no filler words. It conveys the core operation and selection criterion immediately, earning its place without wasted content.

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 one-parameter retrieval tool, the description is minimally adequate: the schema already marks post_id as required, and the description identifies the operation. However, with no output schema and no annotations, the absence of any mention of return shape or failure behavior makes the definition only partially complete for an agent deciding whether and how to invoke it.

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%, and the description only repeats the concept of 'by ID' without explaining the expected format, source, or constraints of post_id. The parameter name itself already conveys most of the meaning, so the description adds almost no semantic value 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?

The description uses a specific verb ('Get') and names the exact resource ('details of a single Facebook post') selected by ID. This clearly distinguishes the tool from siblings like fb_list_posts, fb_create_text_post, and fb_delete_post without requiring schema inspection.

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 the tool is for retrieving one specific post when you already have its post_id, which is clear enough from the phrase 'by ID.' However, it does not explicitly contrast with alternatives such as fb_list_posts for fetching multiple posts or fb_get_comments for related data, so usage guidance is mostly implicit.

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