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

Annotations already declare readOnly=false, idempotent=true, and destructive=false. The description adds the auth requirement (organizer key) and clarifies the voting toggle behavior, which is genuinely useful beyond the annotations. However it does not say what a settings change affects, whether changes are reversible, or how partial updates behave across the 14 parameters.

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?

It is very short and front-loads the purpose, but the run-on 'voting Needs the organizer key' (missing punctuation) reads as a structure defect. Content is minimal rather than tight, so it is barely 'appropriately sized' for a 14-parameter tool.

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 14-parameter mutation tool with 43% schema coverage and no output schema, the description is far too thin. It names the auth prerequisite and the voting toggle but leaves the bulk of configurable settings undocumented, so an agent lacks enough to invoke it confidently.

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 description coverage is only 43% across 14 parameters, so the description must carry more of the semantic load, yet it adds almost nothing. 'end / reopen voting' loosely maps to the closed parameter, but fields like ipLimit, results, opensAt, closesAt, allowChange, and requireBallot remain unexplained in both the schema and the description.

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 ('Change settings') plus a distinct capability ('end / reopen voting'), so an agent can tell it is the generic settings-mutation tool. It does not explicitly differentiate itself from siblings like set_questions or set_answer_key, which also mutate contest state, so it falls short of a 5.

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?

Provides a critical prerequisite ('Needs the organizer key') but gives no when-to-use vs when-not guidance and names no alternatives. Usage is only implied by the generic 'settings' scope. Adequate but with clear gaps.

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