promoted_posts

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

With no annotations, the description carries the behavioral burden. It discloses the return shape ('Returns {count, posts}') and implies a read-only operation via 'Fetch,' but it does not explain what the 'full' parameter changes, pagination behavior, or any authorization requirements.

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 efficient sentence with three front-loaded clauses: action, required/optional parameters, and return shape. There is no filler or redundant wording.

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 tool with no annotations and no output schema, the description leaves a meaningful gap: the 'full' parameter is never explained, which could affect how an agent invokes the tool. There is also no mention of what 'city' filters or how results are ordered.

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%, so the description must compensate. It identifies tag as required and city as optional, but it restates what the schema already encodes via required/default. It omits the 'full' boolean entirely and does not clarify the semantic role of 'city' or 'full' beyond their names.

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 ('Fetch') and a specific resource ('promoted-post carousel for a tag'), which clearly distinguishes this from sibling tools like fetch_feed or search. It also states the required scope parameter, leaving no ambiguity about what the tool returns.

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 fetch_feed, related_tags, or search. The description only mentions required/optional parameters, which is operational detail, not usage criteria.

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