Get Campaign Email Wave

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds meaningful context beyond annotations by noting that the result includes delivery uncertainty and cancellation availability, though it does not explain auth, rate limits, or error behavior.

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 front-loaded sentence with no wasted words. It states the core action and adds relevant return-context details efficiently.

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 read-only tool with one parameter and no output schema, the description covers the basic purpose and hints at returned fields. However, without an output schema, it does not explain the wave object contents, identifier source, or failure behavior, leaving some gaps.

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?

There is one required wave_id parameter, but the schema description coverage is 0% and the description adds no parameter-level meaning beyond implying a single wave is read. The schema does constrain wave_id as a UUID, but the description does not compensate for the lack of schema 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 uses a specific verb, "Read", and a specific resource, "one campaign email wave", making the single-item scope clear against the list endpoint. It adds useful detail about delivery uncertainty and cancellation availability, but does not explicitly name siblings like list_campaign_email_waves or cancel_campaign_email_wave.

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 description states what the tool does but gives no explicit guidance on when to use it versus list_campaign_email_waves, cancel_campaign_email_wave, or retry_campaign_email_wave. An agent can infer it is for fetching one wave by ID, but the description does not say so or provide exclusions.

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