humansurvey-mcp

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

Without annotations, the description carries the full burden and successfully discloses: destructive/permanent nature, return value ('final response count'), and operational limitation with workaround. Lacks auth requirements or failure modes, but covers critical safety traits well.

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?

Four sentences cover purpose, usage conditions, return value, and irreversibility constraints with zero waste. Information is front-loaded with the primary action, followed by contextual guidance.

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?

Comprehensive for a 1-parameter destructive tool lacking output schema: description compensates by stating the return value, explains the permanent nature, and provides the external reopening workaround. Appropriate level of detail for complexity.

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% with clear parameter description ('The survey ID to close'), establishing baseline 3. The description adds no additional parameter syntax, format details, or examples beyond the schema.

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 ('Permanently close'), resource ('survey'), and outcome ('no longer accepts new responses'), clearly distinguishing this from siblings create_survey, get_results, and list_surveys.

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?

Provides explicit when-to-use conditions ('when you have enough responses or the data collection window has passed'), warns against use when reopening might be needed ('irreversible via MCP'), and names the alternative reopening method ('PATCH /api/surveys/{id}').

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