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

Annotations only give the generic safety profile (not read-only, not idempotent, not destructive, closed-world). The description adds genuinely non-derivable behavior: a 5-per-day-per-connection rate limit, the return of a public link plus a one-time claim link valid 24 hours, the organizer-dashboard grant, and the explicit security instruction never to ask for or share the organizer 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?

The action and its auth prerequisite are front-loaded in the first clause, and every clause carries information (scope, rate limit, outputs, security rule, alternative). It is a dense compound sentence with an inline URL, which slightly hurts scannability but does not waste words.

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 13-parameter creation tool with no output schema, the description usefully covers auth scope, rate limit, resulting links and the fallback tool, so an agent knows the preconditions and the side effects. It does not say which parameter groups each kind needs (entries for contests/hunts, questions for surveys/quizzes), a gap partially absorbed by the schema's field descriptions.

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 77% and the schema already carries the meanings of kind, entries, questions, categories, mode, results and closesAt. The description adds no parameter-level guidance beyond what the schema documents (e.g. it never explains which parameters are required per kind), so this sits at the baseline the rubric prescribes for high 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?

The description states a specific action (create now, immediately manageable on this connection) and the resource is unambiguous from the title and the 'kind' enum context. It explicitly positions itself against the sibling draft_contest, so an agent can route between the two without opening either schema.

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 names the prerequisite (signed-in connection with Manage scope), the condition that selects a different tool ('Without signing in, use draft_contest'), and the constraint that this connection can manage the result right away. Nothing about when to use versus when not to use is left to inference.

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