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 behavioral burden. It discloses only that the operation retrieves a post, but does not mention required permissions, error behavior, rate limits, or any side-effect profile. This is not a contradiction, but it is thin.

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 one short sentence with no filler, front-loading the verb and the object. Every word contributes to the meaning, which is appropriate for a simple single-parameter fetch tool.

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?

Given the low complexity, one self-explanatory required parameter, and the presence of an output schema, this is minimally viable. The clear gaps are usage guidance, permission requirements, and post_id format details, but an agent can reasonably select and invoke this tool with the available information.

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 does not mention post_id or its format. However, the single parameter is already named post_id and the phrase 'publication Facebook précise' weakly maps to the need for a specific post identifier, so minimal meaning can be inferred.

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 'Récupère une publication Facebook précise' uses a specific verb and resource: it retrieves one specific Facebook post. This clearly distinguishes it from sibling tools like list_page_posts or get_post_insights.

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 guidance about when to use this tool instead of alternatives such as list_page_posts or get_post_insights. The word 'précise' weakly implies fetching a single post by ID, but no explicit context, exclusions, or alternative routing is provided.

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