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

Annotations already cover read-only, idempotent, and non-destructive behavior. The description adds the CSV shape, the download-link return, and the permission requirement, which are useful behavioral details. It does not mention edge cases like empty exports, but that is minor.

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 sentences, front-loaded with the action and output, then requirements. No filler; every sentence 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?

For a simple one-param export tool, the description covers purpose, output format, return type, and permissions. No output schema exists, so the return description is valuable. It does not cover error cases, but that is not essential.

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 0%, so the description must compensate. It only says 'Requires community_id' and ties it to the community context, but does not explain what the ID is or how to obtain it. For a single self-named parameter, this is adequate but not rich.

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 (Export), resource (community signup answers), format (CSV), and output (download link). It also specifies the row/column structure, distinguishing it from sibling export tools like export_guest_list_csv and export_form_responses_csv.

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 clear context: requires community_id and creator/admin permission, and is read-only. It does not explicitly name alternatives or when-not conditions, but the community-scoped description implies when to use it versus generic form or guest list exports.

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