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 does add useful context: the scope restriction 'you are party to' (implying authorization/viewing restrictions) and the conditional 'if available' (indicating the summary may or may not be present). However, it does not explain error behavior, what happens when the campaign does not exist, or whether any side effects occur (though it appears to be a read operation).

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 sentence, which is appropriately brief and front-loaded with the core purpose. However, the leading '[Buy]' label is unexplained and may introduce ambiguity or noise. While not disruptive, it is not fully earned, so the structure is good but not flawless.

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 single-get tool with one parameter and no output schema, the description covers the key aspects: what it retrieves (one campaign booking), the access scope (party to), and the inclusion of a delivery/attribution summary when available. It does not describe return structure in detail, but given the simplicity and the mention of the summary, it is reasonably complete for an agent to invoke correctly.

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 input schema has one parameter, campaignId, with no description, and the description does not explicitly explain what campaignId refers to or how it relates to the 'campaign booking'. Schema description coverage is 0%, so the description must compensate, but it only refers to the resource as 'one campaign booking' without stating that campaignId is the identifier. The agent is left to infer the connection.

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 the specific verb 'Get' with the resource 'one campaign booking' and adds a scope constraint ('you are party to'). This clearly distinguishes it from sibling tools like list_campaigns (plural listing) and buy_campaign/create_campaign (creation). The phrase 'including delivery/attribution summary if available' further clarifies the tool's specific output focus.

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?

No explicit guidance is provided about when to use this tool versus alternatives. There is no mention of when not to use it, nor any reference to related tools such as list_campaigns or get_attribution. Usage is only implied by the verb 'Get', which is insufficient for an agent deciding between similarly named tools.

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