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

Annotations only carry destructiveHint=false, so the description does the heavy lifting: login/organizer permission required, 20k cap, returns only a signed link, link valid 10 minutes, opens successfully once, re-obtainable on expiry, permission re-verified on open, plus a truncation notice at the row cap. This is far beyond what annotations provide.

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?

Front-loads the permission/behavior profile in brackets, then the workflow, then the link rules and privacy reminder. Every sentence carries information, though the density makes it slightly harder to scan than an ideal two-tier structure.

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 an export-link generator with one param and no output schema, the description covers what an agent needs: prerequisites, row cap, that the return is a URL not CSV content, link lifetime and single-use behavior, and the privacy/truncation caveats.

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?

There is a single parameter (slug) with 100% schema description coverage, so the schema already documents it. The description adds no extra meaning about the slug beyond what the schema provides; baseline 3 applies when schema coverage is complete.

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 (issue a signup export link) plus its defining scope: up to 20,000-row CSV, returns only a one-time signed URL and never the CSV body. It also names the two sibling tools (list_signup_submissions, bulk_review_signup_submissions) it must not be confused with.

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?

Gives an explicit sequence: list_signup_submissions to see count/overview → user confirms full-table export → this tool → hand the url back as-is. It also states the alternative for the other use case (per-person handling via bulk_review_signup_submissions), so selection is unambiguous.

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