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

Annotations already declare read-only, idempotent, closed-world, non-destructive. The description adds genuinely new behavioral context: results are truncated at 500 rows and ordered newest-first, quiz responses carry scores, and an organizer key is required. It stops short of saying what happens past 500 (silent truncation vs. pagination).

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 short sentences with zero filler; the scope constraints (ordering, cap, quiz scores) are front-loaded and the precondition is last. 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, the description does the work of describing the return payload (ordered responses, up to 500, with quiz scores) and the auth requirement. It is complete enough to call correctly, though it omits overflow behavior beyond the 500 cap.

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 documented in the schema with both pattern and a worked example URL. The description adds no meaning beyond the schema, so 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?

States a specific verb+resource ('Survey responses') with concrete scope modifiers: newest-first ordering and a 500-row cap, plus conditional content for quizzes (scores included). It does not, however, differentiate itself from close siblings like get_results or export_csv, so the agent must infer the boundary.

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?

The only guidance is a prerequisite ('Needs the organizer key'), which is a prerequisite rather than a when-to-use rule. Nothing says when to choose this over get_results (aggregate results) or export_csv (file export), and no exclusions are given.

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