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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered by structured data. The description adds only the scope of returned content (sequence, schedule, settings), with nothing about not-found behavior, permissions, or error handling.

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?

A single short sentence with no filler, and the resource is front-loaded. It is efficient, though the brevity is partly under-specification rather than discipline.

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 get-by-id tool with annotations and no output schema, the description is minimally adequate: it identifies the resource and the rough shape of the response. It omits identifier expectations and failure modes, which the empty schema descriptions do not cover.

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 a single required parameter, 'id', and schema description coverage is 0%, so the description carries the burden of clarifying it. It says nothing about which identifier is expected (campaign id format, where it comes from), leaving the parameter documented only by its bare name.

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 names a verb (Get) and resource (campaign) and hints at returned content (sequence, schedule, settings), so the purpose is inferable. However, it is a verbatim restatement of the title and does nothing to separate this tool from siblings like list_campaigns, get_campaign_stats, or get_campaign_analytics.

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 when-to-use guidance at all. With siblings such as list_campaigns, get_campaign_analytics, get_campaign_stats, and get_launch_checklist, the agent gets no signal about when a single-campaign fetch is appropriate versus those alternatives.

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