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 value by describing the payload contents (a configuration preview with the listed sections), which matters because there is no output schema; it does not mention error/not-found or auth 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?

Two compact, front-loaded clauses with no filler. The trailing 'GET /api/v1/campaignSite/{uuid}' is mildly redundant with the parameter name but is short enough not to hurt readability.

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?

With no output schema, the enumeration of returned configuration areas gives an agent a good preview of what it will get. Only error behavior and any access-permission notes are absent, which are minor for a single-resource read.

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?

Only one parameter and schema description coverage is 100%, so the schema already documents campaign_site_uuid fully. The description's 'by UUID' adds minimal meaning beyond that, matching the baseline for full schema coverage.

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 verb and resource ('One campaign site by UUID') and enumerates the returned configuration sections (payment options, goals, form, homepage, fundraiser settings). That clearly distinguishes it from sibling funraise_list_campaign_sites.

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?

Usage is implied by 'by UUID' versus the plural list tool, but the description never explicitly says when to use this instead of funraise_list_campaign_sites or what to do if the UUID is unknown. No exclusions or prerequisites are stated.

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