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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety behavior is fully covered structurally. The description adds only the payload hint (goal, status, health) and says nothing about missing-campaign errors or how 'health' is derived.

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 economical fragment with the key scope word ('One') front-loaded and zero padding. It is arguably over-compressed rather than bloated, but nothing is wasted.

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?

The tool is simple and richly annotated, and there is no output schema, so the description's mention of goal/status/health is the only return-value signal - which is thin. It lacks error behavior and any hint of what a campaign record contains beyond the three listed fields.

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?

One required parameter with 100% schema description coverage, so the schema already explains campaign_id as an existing campaign id. The description adds no format, source, or lookup guidance beyond that, which is the expected baseline when schema coverage is complete.

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?

States a specific resource and scope: a single campaign, returning goal, status, and health. The singular 'One campaign' implicitly contrasts with the sibling list tool crm_campaigns, so an agent can distinguish them, though the contrast is never made explicit.

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 statement of when to use this versus crm_campaigns (list), crm_update_campaign, or crm_set_campaign_status. The only signal is the singular phrasing plus the required campaign_id in the schema, so usage must be inferred.

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