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

Annotations already cover safety (readOnly, idempotent, non-destructive), so the extra value here is real: it discloses the authorization requirement ('Needs the organizer key') and explains the semantics of campaign.note as a moderator message to relay to the organizer. That is behavioral context an agent cannot get from the schema or annotations.

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?

Dense and front-loaded with payload contents, then the auth requirement and the non-obvious note semantics. The opening sentence is slightly malformed (title and content run together), but every clause earns its place.

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 in play, the description has to convey what comes back, and it does by listing the dashboard sections plus the special campaign.note field and the auth prerequisite. It stops short of describing size or pagination, but nothing critical for correct invocation is missing.

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 coverage is 100% and the slug parameter is documented with a concrete URL example, so the schema carries this dimension. The description adds nothing about slug format or behavior.

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 enumerates what the dashboard returns (settings, entries with vote counts, ballot tickets, fairness signals, survey/hunt data), which is more specific than the title's 'everything on the organizer dashboard'. It reads as a read/retrieval tool and is distinguishable from narrower siblings like get_results or get_campaign, though it never states a verb outright.

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 only implied: an agent can infer this is the broad 'get the whole dashboard' call versus narrower siblings, but nothing says when to prefer it over get_campaign or get_results, or whether it's expensive/heavy. No exclusions or alternatives are named.

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