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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states that the tool lists messages, without any details on pagination, ordering, access controls, or potential side effects—all of which are unknown to the agent.

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 concise sentence that is easy to parse. However, the leading '[Buy]' prefix is unexplained and could be seen as extraneous noise, slightly reducing the overall efficiency.

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 absence of annotations and output schema, the description is too sparse for the agent to understand pagination, result format, or edge cases like empty threads. It provides minimal context beyond the fundamental action.

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?

The schema has 0% description coverage, and the description adds no explanation of the parameters. While 'campaignId' is semantically tied to the 'campaign booking thread', 'limit' is entirely unexplained. The description fails to compensate for the lack of parameter documentation.

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 clearly states the tool's action ('List messages') and the resource ('a campaign booking thread'), with context that it involves advertiser and publisher. This distinguishes it from sibling tools like send_message, which handles the opposite action.

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?

The action is unambiguous, implying use when the agent needs to retrieve messages on a thread. However, there is no explicit guidance on when to use this tool versus alternatives, no exclusions, and no mention of prerequisites or context that would help choose between this and similar list tools.

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