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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint=false, so the safety profile is covered. The description adds real value beyond them by disclosing the organizer-key authorization requirement and that fairness signals are returned grouped and hashed, but says nothing about payload size, pagination, or what happens without the key.

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 with the content inventory front-loaded and the auth caveat last. The first sentence is a fragment-style list, which is terse but slightly awkward as prose.

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 read-only aggregate tool with no output schema, enumerating the returned sections plausibly substitutes for a return-value description, and the auth requirement is stated. Missing only edge behavior (empty/unauthorized cases) and overlap with sibling endpoints.

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 single slug parameter is fully documented with a pattern and URL example, so the schema carries the parameter burden. The description adds no formatting or fallback detail for slug, only the separate credential note; baseline 3 applies.

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 specific aggregate resource and enumerates its contents (settings, entries with vote counts, ballot tickets, fairness signals, survey/hunt data), so an agent knows this is a one-stop read of organizer state. It does not explicitly differentiate from siblings like get_results, get_campaign, or list_responses, which likely overlap on some of the same data.

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 a prerequisite ('Needs the organizer key') but gives no when-to-use guidance and never names an alternative among the many overlapping read tools (get_campaign, get_results, list_responses). The agent must guess whether this is a superset replacement or a separate view.

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