Get one post

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description adds the returned detail fields, which is useful without an output schema, but it omits account scoping behavior, missing-media errors, and any rate-limit or permission context.

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?

A single front-loaded sentence with no filler. The field list is dense but every item is relevant to what the tool returns.

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 read tool, the annotations cover the safety profile and the description usefully lists return contents in the absence of an output schema. It still lacks sibling routing guidance and leaves media_id and account semantics largely to the schema.

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 coverage is only 50%: the account parameter is documented in the schema, but the required media_id has no schema description. The description implies that media_id identifies a post, reel, or carousel, but adds no format or account-selection semantics, so it does not compensate for the gap.

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 opens with 'Full details of one post, reel or carousel' and enumerates the returned fields, so the agent can tell this retrieves a single media item. It does not explicitly distinguish itself from siblings such as list_media or get_media_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 explicit when-to-use, when-not-to-use, or named alternative. 'One post' only implicitly suggests fetching details for a known media_id after enumeration, leaving the agent to infer the contrast with list_media and get_media_insights.

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