List structured posts

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is clear. The description adds only the profile scoping and does not disclose pagination behavior, filtering behavior, or what the returned structured posts include. It adds almost no behavioral context beyond the structured fields.

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 sentence is concise and front-loaded, but it is under-specified rather than tightly scoped. It avoids waste but omits information that would make the sentence genuinely useful, so it sits at the minimum viable level.

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 seven parameters, pagination controls, no output schema, and many sibling tools, this description is far too thin. It does not explain filtering, pagination, or how the results relate to the broader Reddit Ads post hierarchy, leaving the agent to infer most usage details.

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 57%, and the description itself only implies the profile_id parameter. It does not explain the id, type, source, max_pages, page_size, or page_token parameters. It fails to compensate for the undocumented parameters and adds no meaning beyond the schema's own descriptions.

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 gives a specific verb ('List') and a resource ('structured posts'), and adds the scoping condition 'on a profile'. However, it does not distinguish this tool from its close siblings such as reddit_ads_list_posts or reddit_ads_get_structured_post, so an agent cannot tell from the description alone why it should choose this one.

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 on when to use this tool versus alternatives like reddit_ads_list_posts, reddit_ads_get_structured_post, or reddit_ads_update_structured_post. The description states what it does but provides no context, prerequisites, or exclusions.

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