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

Beyond the annotations (readOnlyHint=true, destructiveHint=false), the description adds the permission constraint (creator or admin) and details the response content and ordering. This provides context beyond what annotations convey, while remaining consistent with them (Read-only aligns with readOnlyHint).

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 description is two sentences, front-loaded with the main action and key details, with no redundant words. It efficiently conveys purpose, permissions, and response characteristics.

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 single-parameter read tool without an output schema, the description gives a useful high-level summary of the response but omits pagination, limits, or the exact response shape. While adequate for a simple list operation, the absence of these details leaves some uncertainty given no structured output definition.

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?

With schema description coverage at 0%, the description must explain the parameter. It only states 'Requires community_id', which restates the requirement without adding meaning about what the ID represents or any format details beyond the schema's type and length constraints. This fails to compensate for the absent schema descriptions.

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 clearly states the tool reads members' answers to a community's signup form, specifying what is returned (who, when, each answer by question) and ordering (newest first). It distinguishes this from generic form-response tools by explicitly mentioning 'community's signup form', though it does not name an alternative sibling.

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 description provides no guidance on when to use this tool versus similar siblings like list_form_responses or export_community_signup_responses_csv. It only mentions a permission requirement and the need for community_id, without hinting at alternatives or exclusions.

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