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

Annotations already declare readOnly, idempotent, and non-destructive behavior, so safety is covered. The description adds a genuinely useful behavioral fact beyond the annotations: the call returns null when no dataset is attached to the account. It does not cover error modes for an invalid profile_id, which is minor for a read-only getter.

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?

Two tight sentences, front-loaded with the resource being read, followed by the workflow dependency. Every clause earns its place; no filler or restatement of the name.

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?

There is no output schema, so the description helpfully discloses the return value (the dataset id) and its null case. Combined with read-only annotations and a fully documented single parameter, an agent has everything needed to call this 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?

Schema description coverage is 100% and there is only one parameter, so the schema already documents profile_id as the profile hashid of a WhatsApp profile. The description's mention of the WhatsApp Business Account restates that relationship rather than adding syntax, format, or sourcing guidance; baseline 3 is appropriate.

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 (Read) and a precise resource (the Conversions API dataset id attached to the WhatsApp Business Account), which an agent can distinguish from the sibling whatsapp_dataset_create. It stops short of explicitly naming that sibling as the alternative, so differentiation is implied rather than stated.

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?

It states the purpose in a downstream workflow: the value is 'Needed for whatsapp_conversion_event_send', which tells the agent when to reach for this tool (before sending a conversion event). There are no exclusions or negative triggers, but the dependency context is a clear, actionable usage signal.

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