Get structured post

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

Annotations declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond that: it does not clarify return shape, whether the id refers to a structured post in the same namespace as regular posts, or error behavior for a missing/invalid id. With the lower bar set by annotations, this is still a bare minimum.

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 single short sentence is not concise so much as under-specified; it is a tautology of the title with no informational payload. Brevity here reflects missing content rather than efficient structure.

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 lookup tool with no output schema, a 0%-covered parameter, and no behavioral detail, the description leaves the agent without enough information to call it correctly. Nothing describes what is returned or how errors are surfaced.

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 single parameter post_id is undocumented in both schema and description. The description does not state the id's format, source, or whether it is the structured post id returned by list_structured_posts, so it fails to compensate for the coverage 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 'Get a structured post.' is a verbatim restatement of the title and tool name, adding no distinguishing detail. It does not differentiate this tool from siblings like reddit_ads_get_post, reddit_ads_list_structured_posts, or reddit_ads_update_structured_post, leaving the agent to infer what a 'structured post' actually is.

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 when-to-use guidance, no mention of prerequisites (e.g., authentication or lookup of an existing post id), and no routing to alternatives such as list_structured_posts for discovery or get_post for regular posts. Usage is only implied by the word 'Get'.

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